AdGuard DNS Not Working | Fixes That Stick Fast

When ad blocking drops off overnight, it usually isn’t that AdGuard DNS “stopped.” More often, your device switched to a different resolver after a router reboot, a VPN toggle, a carrier handoff, or a browser setting change.

This walkthrough helps you confirm which DNS is active, remove common override points, then set up AdGuard DNS in a way that stays put on Wi-Fi and on mobile data.

Start By Proving Which DNS Server You Are Using

Before changing settings, get one hard fact: which resolver answers your queries right now. If you skip this step, you can spend time tweaking the wrong layer.

Check On Windows

Open Command Prompt, then run a basic lookup. The “Server” line shows the resolver used for that test.

• Run nslookup — Type nslookup example.com and read the Server line at the top.
• Flush cached answers — Run ipconfig /flushdns, then repeat the lookup.
• Repeat per adapter — Test on Wi-Fi, then on Ethernet, to spot per-connection DNS.

Check On Android And iPhone

Phones add one more twist: Private DNS or encrypted DNS can override the DNS you set on Wi-Fi. A VPN app can also route DNS through its own tunnel.

• Toggle airplane mode — Turn it on for 10 seconds, then off, to force a fresh network handshake.
• Verify Private DNS — On Android, set Private DNS to Off, or set it to a hostname you trust.
• Check VPN DNS settings — Inside the VPN app, look for a DNS option and set it to system or AdGuard.

Check On Your Router Or Modem

If you set DNS on the router and things still feel off, confirm the router is handing out the servers you expect. Some routers keep separate DNS fields for WAN and LAN. Some have a “DNS relay” feature that makes every device show the router IP, even when the router forwards to AdGuard.

• Review DHCP DNS — In LAN or DHCP settings, confirm the DNS fields match the AdGuard servers you chose.
• Disable DNS relay — If your router offers DNS relay or DNS proxy, turn it off so clients receive real upstream DNS.
• Reboot after changes — Restart the router so the DHCP service hands out fresh settings.

Check Inside Your Browser

Some browsers can send DNS over HTTPS to their own provider. That can make it look like AdGuard DNS is failing, even when it’s working for other apps.

• Find Secure DNS — In browser settings, locate Secure DNS or DNS over HTTPS.
• Disable provider override — Turn it off, or set it to follow system settings if available.

Use The Right AdGuard DNS Servers And Modes

Once you know you’re not using AdGuard, enter the right servers for the mode you want. Pick one profile, then use it everywhere you configure DNS so tests stay consistent.

IPv6 can override IPv4 on many networks. If your router or device uses IPv6 DNS, add the matching IPv6 resolvers too, or disable IPv6 DNS assignment on that network. For AdGuard’s default profile, the IPv6 servers are 2a10:50c0::ad1:ff and 2a10:50c0::ad2:ff.

If you want encrypted DNS, AdGuard commonly uses the hostname dns.adguard-dns.com, with DNS-over-HTTPS at https://dns.adguard-dns.com/dns-query.

AdGuard DNS Not Working On Wi-Fi And Mobile Data

Most reports that look like “adguard dns not working” boil down to one of three things: you’re not using AdGuard at all, you’re bypassing it, or the network is rewriting DNS behind your back.

Router DNS Is Set, Yet Devices Still Use Something Else

Setting AdGuard DNS on the router is a solid baseline, yet some devices hold on to older values or prefer IPv6 resolvers learned from the router.

• Renew the lease — Disconnect and reconnect Wi-Fi so the device requests DNS again.
• Check IPv6 DNS — Set AdGuard IPv6 servers, or disable IPv6 DNS on the LAN if you don’t need it.
• Restart the device — A reboot clears stuck resolver state on many phones and TVs.

Old DNS Is Still Cached

DNS caching is normal. It keeps browsing fast, yet it can hide your fixes for a while. If you changed DNS and results didn’t budge, clear caches at the points that matter, then retest with a fresh query.

• Flush system cache — On Windows, run ipconfig /flushdns. On macOS, restart the device if you don’t want to use Terminal.
• Restart the browser — Close it fully, reopen, then test again so old connections don’t mask the change.
• Wait out short TTLs — Some records take a few minutes to refresh even after you flush caches.

Your ISP Or Wi-Fi Network Redirects DNS

Some public networks redirect DNS traffic on port 53. You set a custom resolver, yet the network answers with its own service.

• Switch to encrypted DNS — Use DNS-over-HTTPS or DNS-over-TLS so port 53 redirection can’t catch your requests.
• Compare another network — If it works on cellular but fails on one Wi-Fi, that Wi-Fi is the blocker.

A VPN Or Security App Is Taking Over DNS

Many security tools run a local DNS proxy, then forward queries to their own upstream. That can override your router and device settings.

• Disable DNS features — Turn off DNS filtering inside the app, not just the main toggle.
• Set the app’s DNS — If the app offers a DNS choice, set it to system or AdGuard.
• Reboot after changes — DNS proxies can keep sockets open until a restart.

Step By Step Setup That Stays Stable

You can configure AdGuard DNS at more than one layer. The more places you set it, the fewer surprises you get. Build from the layer you control best.

Option A Set It On The Router For Whole Home Setup

This setup keeps DNS consistent across phones, TVs, and guests. It also reduces per-device edits.

• Open router LAN settings — Find the DHCP or LAN page where DNS servers are entered.
• Enter AdGuard DNS servers — Use the profile you picked, then save and apply.
• Restart the router — Let clients reconnect and pull the new DNS settings.

After that, retest with nslookup on a computer, then test a few ad-heavy sites. If the active resolver still isn’t AdGuard, switch that device to encrypted DNS by hostname so the local network can’t rewrite it.

Option B Set It Per Device For Travel And Mixed Networks

Per-device DNS can be steadier on hotels and hotspots. It also lets you control filtering per person without touching the router.

• Edit DNS on the network — On iPhone, set DNS to Manual under the Wi-Fi network. On Android, use Private DNS for hostname-based encrypted DNS.
• Use the encrypted hostname — For Android Private DNS, enter dns.adguard-dns.com.
• Retest right away — Load an ad-heavy page, then run your Windows nslookup check if you can.

Option C Use Encrypted DNS On Windows And macOS

Encrypted DNS helps when a network redirects classic DNS traffic. It also reduces snooping on public Wi-Fi. The idea is to use the same AdGuard profile, just carried over an encrypted channel.

• Use a supported hostname — Choose dns.adguard-dns.com when your system asks for a resolver name.
• Enable encryption when offered — In Windows network DNS settings, turn on encrypted DNS if your build supports it for your configuration.
• Confirm after a reboot — Restart, then run the same nslookup test to confirm the resolver didn’t revert.

If your system doesn’t offer an encryption toggle, you can still use the AdGuard IP servers with classic DNS. In that case, put your effort into removing VPN, browser, and router overrides so the requests reach AdGuard consistently.

When Ads Still Show Up Even With The Right DNS

DNS-level blocking has limits. It can block domains. It can’t remove ad elements delivered from the same domain as the site itself. Some apps also behave differently than browsers.

Know What DNS Blocking Can And Can’t Do

• Expect domain blocks — Third-party ad servers are a great match for DNS filtering.
• Expect misses on same-site ads — If a site serves ads from its own domain, DNS can’t split ads from content.
• Expect app edge cases — Some apps cache endpoints or use fallback paths that blur results.

Use No Filtering As A Control Test

If a site breaks, it’s smart to confirm a block is involved before you change five settings. The no filtering profile gives you a clean comparison in minutes.

• Switch profiles briefly — Use the non-filtering servers for a short test window.
• Retest the same site — If the issue disappears, filtering is part of the cause.
• Switch back — Return to your chosen profile once the test is done.

Troubleshooting Map For Fast Wins

Match your symptom to a likely cause, then apply a targeted fix. This keeps your setup tidy and speeds up diagnosis.

Keep It Working Over Time

The goal is to avoid ending up back at “adguard dns not working” after the next update or network change. A few habits prevent most regressions.

• Save your settings — Keep the two IPs and any hostname you use in a note.
• Retest after big changes — After OS updates, router firmware updates, or VPN installs, run one nslookup check.
• Avoid double management — Pick one layer as your source of truth, then keep other layers aligned.
• Watch for IPv6 drift — If your ISP enables IPv6, add IPv6 resolvers or disable IPv6 DNS on the LAN.

If your setup still fails, isolate the override point: test another network, test another device, then re-enable apps one by one. Once you find the switch that changes the resolver, you can lock AdGuard DNS back in and keep it steady.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback