Fix DNS Issues on Your Router

Signs of a router DNS problem

• All devices fail at once — If every phone, laptop, and smart device loses DNS simultaneously, the router is the common link.
• Ping works but browsing fails — You can ping IP addresses (e.g., ping 1.1.1.1) but cannot load websites by name.
• Slow DNS resolution — Pages take 5-10 seconds to start loading, then load quickly once they begin. This points to DNS timeout before fallback.
• NXDOMAIN redirects — Mistyped domains show your ISP's search page instead of a browser error. This indicates DNS hijacking.

Step 1 — Restart your router

The simplest fix for most router DNS issues:

1. Unplug the router from power.
2. Wait 30 seconds (this ensures the RAM clears completely).
3. Plug it back in.
4. Wait 2 minutes for it to fully boot and establish the ISP connection.

A power cycle clears the router's DNS cache, resets NAT tables, and forces a fresh DHCP lease from your ISP. This alone fixes most transient DNS issues.

If you have a separate modem, restart it first, wait for it to connect, then restart the router.

Step 2 — Log into the router admin panel

Open a browser and enter your router's admin address. Common addresses:

• 192.168.1.1 — Most routers (Linksys, ASUS, TP-Link)
• 192.168.0.1 — Some Netgear, D-Link, Belkin routers
• 10.0.0.1 — Some Xfinity/Comcast gateways
• 192.168.1.254 — Some BT and AT&T gateways

If you do not know the address, open a command prompt and run ipconfig (Windows) or check Settings > Wi-Fi > Router (iOS/macOS). The Default Gateway is your router's IP.

Default credentials are usually printed on a sticker on the router. If you changed them and forgot, a factory reset (Step 7) will restore defaults.

Step 3 — Change DNS servers in WAN settings

The most impactful fix — replacing your ISP's DNS with a reliable public resolver:

1. In the admin panel, navigate to WAN, Internet, or Network settings (label varies by brand).
2. Find the DNS Server fields (sometimes under Advanced settings).
3. Change from Get automatically from ISP to Use the following DNS.
4. Enter 1.1.1.1 as Primary DNS and 8.8.8.8 as Secondary DNS.
5. Click Save or Apply.

The router may reboot. Once it comes back, all devices on the network will use the new DNS servers automatically (via DHCP).

For detailed router instructions, see our router DNS setup guide.

Step 4 — Check DHCP settings

Your router assigns DNS servers to devices via DHCP. If this is misconfigured, devices get wrong or empty DNS settings.

1. In the admin panel, go to LAN or DHCP Server settings.
2. Verify DHCP Server is Enabled.
3. Check the Primary DNS and Secondary DNS fields.

These fields should either be the router's own IP (meaning it proxies DNS from the WAN settings) or your chosen DNS server IPs. If they are blank or point to an old server, that is your problem.

After changing DHCP DNS, devices will pick up the new settings when their lease renews. To force it immediately, disconnect and reconnect each device from Wi-Fi.

Step 5 — Update router firmware

1. In the admin panel, go to Administration, System, or Firmware Update.
2. Click Check for updates or upload firmware manually from the manufacturer's website.
3. Apply the update and wait for the router to reboot (do not unplug during this process).

Outdated firmware can cause DNS resolution bugs, buffer overflows in the DNS proxy, and incompatibilities with DNSSEC-signed responses. Manufacturers regularly patch these issues.

Step 6 — Check for ISP DNS hijacking

Some ISPs intercept all DNS traffic on port 53 and redirect it to their own servers, regardless of what DNS you configured. This is called transparent DNS hijacking.

How to detect it:

1. Set your router DNS to 1.1.1.1 (Step 3).
2. Open our DNS Privacy Check on any device.
3. Run the check and look at the detected DNS resolver IP.
4. If the detected IP is not 1.1.1.1 but belongs to your ISP, your DNS is being hijacked.

To bypass ISP DNS hijacking, use DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) on individual devices, since encrypted DNS cannot be intercepted. See our DoH vs DoT guide for setup instructions.

Step 7 — Factory reset as last resort

If nothing else works, reset the router to factory defaults:

1. Find the Reset button on the back or bottom of the router (small pinhole).
2. Use a paperclip to press and hold it for 10 seconds.
3. Wait for the router to reboot with factory settings.
4. Reconfigure your Wi-Fi name, password, and DNS settings.

Warning: This erases all custom settings — Wi-Fi passwords, port forwarding rules, parental controls, static IPs, and firewall rules. Take note of your settings before resetting.

Step 8 — Consider Pi-hole for network-wide DNS control

For a permanent solution with full visibility into DNS queries across your network:

• Set up Pi-hole on a Raspberry Pi or any Linux device on your network.
• Point your router's DHCP DNS to the Pi-hole IP address.
• Pi-hole blocks ads at the DNS level, logs all queries, and lets you choose upstream DNS servers.

See our Pi-hole setup guide for step-by-step installation instructions.

Test your DNS configuration

After fixing your router DNS, verify the configuration from any device on your network:

• DNS Privacy Check — Verify your DNS resolver identity and detect hijacking.
• DNS Gaming Benchmark — Compare latency to 50+ DNS servers from your network.
• Browse all public DNS servers — Find the best resolvers for your region.

Frequently asked questions

How do I know if my ISP is hijacking DNS?

Configure your router to use a known DNS server like 1.1.1.1, then run the DNS Privacy Check on publicdns.info. If the detected resolver is not 1.1.1.1 but an IP belonging to your ISP, they are intercepting your DNS traffic. Switching to DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) on your devices can bypass this.

Should I set DNS on my router or on each device?

Setting DNS on the router changes it for every device on your network in one place. This is simpler to manage. However, device-level settings override router DNS, so both approaches can coexist. For maximum control, use the router for a baseline and override on specific devices that need different DNS.

Why do all devices on my network have DNS issues at the same time?

If every device fails simultaneously, the problem is either your router, your ISP DNS servers, or your internet connection — not individual device settings. Restart the router first, then check if your ISP is experiencing an outage.

Can I use DNS-over-HTTPS on my router?

Some modern routers support DoH natively (ASUS, Netgear Orbi). Most consumer routers do not. If yours does not support DoH, you can either set DoH on individual devices, use a Pi-hole with Cloudflared as a DoH proxy, or flash custom firmware like OpenWrt which supports DoH.