TP-Link Router DNS Server Not Responding: How to Fix It Fast

You open a browser, type a URL, and get hit with "DNS server not responding" — the internet is technically connected, but nothing loads. If you are on a TP-Link router (Archer series, Deco mesh, TL-WR series, or any other model), this error almost always points to the same cluster of causes: bad DNS settings pushed from your ISP, a stuck DNS cache on the router itself, a firmware bug, or a misconfigured WAN connection. The good news is that every one of these has a concrete fix, and most take under five minutes to apply. This guide walks through each one in order from fastest to most involved, so you can stop wasting time and get back online.

What "DNS Server Not Responding" Actually Means

When your device asks for a website, the first thing it does is contact a DNS resolver to turn the domain name into an IP address. If that resolver does not answer — or answers with garbage — your browser cannot make the connection, even though your router shows a healthy internet link. On TP-Link routers, the DNS resolver address is either assigned automatically by your ISP via DHCP or set manually in the WAN or DHCP settings. Either source can fail.

Common triggers on TP-Link hardware specifically include:

• ISP pushing a broken or unreachable DNS address over PPPoE or DHCP
• The router's own DNS relay cache filling up and refusing queries
• Outdated firmware with known DNS relay bugs (common on Archer C6 and C7 v1-v3)
• Manual DNS entries left over from a previous ISP or network that no longer exist
• IPv6 DNS misconfiguration interfering with IPv4 resolution
• MTU mismatch causing DNS UDP packets to fragment and be dropped

Step 1: Quick Sanity Checks Before Touching the Router

Before logging into the admin panel, confirm the problem is actually DNS and not something else. Open a command prompt (Windows) or Terminal (Mac/Linux) and run a direct IP ping and a DNS query:

If the ping to 8.8.8.8 succeeds but nslookup against your router's IP fails, DNS is broken. If both fail, you have a broader connectivity issue — check the WAN/internet light on your TP-Link router first. If nslookup google.com 8.8.8.8 succeeds (querying Google's DNS directly), it confirms your router's DNS relay or its assigned DNS servers are the culprit, not your physical connection.

On Windows, also flush the local DNS cache in case stale entries are the only problem:

If that alone fixes it, the issue was client-side. If not, move on.

Step 2: Log Into Your TP-Link Router Admin Panel

Open a browser on a device connected to the TP-Link network (wired is more reliable for this). Navigate to one of the following addresses depending on your model:

• Most Archer and TL series: http://tplinkwifi.net or 192.168.0.1
• Some older TL-WR models: 192.168.1.1
• Deco mesh systems: Use the Deco app — there is no traditional web admin panel

Log in with your admin credentials. If you have never changed them, the default username and password are printed on the label on the bottom of the router. Common defaults are admin / admin or a unique password shown on the sticker.

Step 3: Set a Reliable Public DNS Server in WAN Settings

This is the single most effective fix for the majority of TP-Link DNS failures. You are going to override whatever broken DNS address your ISP handed the router and substitute a known-good public resolver.

In the admin panel:

1. Go to Advanced (top menu) then Network then Internet (on newer Archer firmware). On older firmware, go to Network then WAN.
2. Scroll down to the DNS section. You will see fields for Primary DNS and Secondary DNS.
3. Enter the following values (Google Public DNS as primary, Cloudflare as secondary is a solid pairing):

Alternatively, use Cloudflare as primary and Google as secondary if you prefer lower average latency:

Click Save. The router will apply the setting without rebooting. Test immediately by loading a website or running nslookup again. This alone resolves the issue around 60 percent of the time.

Step 4: Fix the DHCP DNS Settings Pushed to Your Devices

Changing the WAN DNS tells the router which servers to use for its own lookups. But if your router is acting as a DNS relay (which TP-Link routers do by default), it forwards queries from your devices to those WAN DNS servers. You also need to make sure the router is handing out its own IP as the DNS server to your devices via DHCP — and that it is configured to actually relay queries rather than silently drop them.

1. Go to Advanced then Network then DHCP Server (or Network then DHCP Settings on older firmware).
2. The Primary DNS field in DHCP settings should show the router's own LAN IP (typically 192.168.0.1). This is correct — devices send queries to the router, which relays them.
3. If someone has previously entered a broken third-party IP in the DHCP DNS fields, clear it and put the router's LAN IP back, or simply enter 8.8.8.8 and 1.1.1.1 directly here if you want devices to bypass the router's DNS relay entirely.
4. Click Save.

After saving, release and renew the IP on your client machine to pick up the new DHCP DNS settings:

Step 5: Reboot the Router the Right Way

A TP-Link router's DNS relay cache can become corrupted, especially after an ISP outage. A browser-based restart clears it more cleanly than a physical power cycle alone:

1. In the admin panel, go to Advanced then System then Reboot.
2. Click Reboot and wait 90 seconds for the router to fully come back up.

If you cannot access the admin panel because DNS is so broken the router itself is struggling, do a power cycle: unplug the power adapter, wait 30 seconds, plug back in. This is less clean but still works for cache-related issues.

Step 6: Check and Correct MTU Settings

This is a less obvious but surprisingly common cause on PPPoE connections (which many TP-Link users in Australia, the UK, and Southeast Asia use). The default MTU for PPPoE is 1480, but some ISPs require 1492 or even lower. When MTU is wrong, large DNS response packets get fragmented and dropped, which looks exactly like a DNS failure.

1. Go to Advanced then Network then Internet.
2. Find the MTU Size field.
3. If your connection type is PPPoE, set MTU to 1480. If it is already at 1480 and you are still having issues, try 1452.
4. For DHCP (cable) connections, the correct MTU is usually 1500.
5. Save and reboot.

Step 7: Disable IPv6 DNS Temporarily

IPv6 DNS misconfiguration is a sneaky cause of "DNS server not responding" on modern TP-Link Archer routers. When a device prefers IPv6 and the router has a broken or missing IPv6 DNS server, every lookup can fail or time out even though IPv4 DNS is fine.

1. Go to Advanced then Network then IPv6.
2. Toggle IPv6 to Disabled.
3. Save and test. If DNS immediately starts working, IPv6 was the culprit.

You can leave IPv6 disabled permanently if your ISP does not require it, or investigate your ISP's IPv6 DNS server addresses to configure it correctly.

Step 8: Update TP-Link Firmware

The Archer C7 v1 and v2, the C6 v2, and several TL-WR series routers shipped with firmware that had known DNS relay stability bugs — the relay would silently stop forwarding queries after several days of uptime. Updating firmware fixes these permanently.

1. Go to Advanced then System then Firmware Upgrade.
2. Click Check for Updates (requires the router to have working DNS, which is the catch — if it is totally broken, download the firmware file manually from tp-link.com using your model number and hardware version printed on the router label).
3. For a manual upgrade, click Browse, select the downloaded .bin file, and click Upgrade.
4. Do not power off the router during the upgrade. It takes 2 to 4 minutes.

Step 9: Factory Reset as a Last Resort

If none of the above steps work, a corrupted configuration file in flash memory may be the cause. A factory reset clears everything and returns the router to a known-good state.

Hold the reset button (usually a pinhole on the back) for 10 seconds until the LED blinks rapidly, then release. Wait 2 minutes for the router to reinitialize. You will need to reconfigure your internet connection from scratch, so have your ISP credentials ready (PPPoE username and password if applicable).

How to Verify DNS Is Actually Working After Your Fix

Do not just open a browser and assume success — cached results can mask a still-broken resolver. Use command-line tools to confirm from the root:

All three should return a valid IP address (like 142.250.x.x for Google). If the first two succeed but the third (querying via your router) fails, the router's DNS relay is still broken — revisit Steps 3 through 5.

You can also use the DNS Lookup tool on this site to verify that external DNS resolvers can reach your domain correctly, which is useful if you are also hosting a website on the connection in question.

How to Prevent This From Happening Again

Once you have a working setup, a few configuration choices will dramatically reduce the chance of this recurring:

• Lock in public DNS on the WAN settings permanently. Never rely solely on ISP-assigned DNS. ISP resolvers go down during outages and maintenance windows far more often than Google or Cloudflare.
• Enable automatic firmware updates if your TP-Link model supports it (Advanced, System, Firmware Upgrade, Auto Update toggle on newer firmware). This ensures DNS relay bug fixes are applied without manual intervention.
• Set a router reboot schedule. Under Advanced, System, Reboot Schedule, set the router to reboot once a week during off-hours (3 AM on Sunday, for example). This clears cache buildup that leads to gradual DNS relay degradation.
• Document your settings. Take a screenshot of your WAN and DHCP DNS configuration after a successful fix. When your ISP changes something upstream six months from now, you will know exactly what your baseline looks like.

When the Problem Is Not the Router at All

If you have worked through every step above and DNS still fails on some devices but not others, the problem is almost certainly device-specific rather than router-specific. Check whether Windows Defender Firewall or a third-party antivirus (Avast, Kaspersky, and Bitdefender are all known to interfere with DNS) is blocking UDP port 53 traffic on the affected machine. On Windows, you can test by temporarily disabling the firewall and running nslookup again. Also check whether a VPN client is running and capturing DNS queries — many VPN clients redirect all DNS through their own tunnel and fail silently when the VPN server is unreachable.

TP-Link DNS errors are fixable in virtually every case without calling your ISP or replacing hardware. Work the steps in order, verify with command-line tools rather than browser intuition, and you will have a clean, reliable DNS setup that does not fall over when your ISP sneezes.