AdGuard DNS not working in India today?

DNS queries not resolving at all

If sites stop opening completely after switching to AdGuard DNS, the first thing to check is whether the correct server addresses are set. For regular filtering use 94.140.14.14 and 94.140.15.15, for non-filtering — 94.140.14.140 and 94.140.14.141. A common mistake is mixing up primary and secondary servers or leaving the old ISP''s DNS in the secondary field. After changing addresses, flush the local DNS cache: on Windows run ''ipconfig /flushdns'', on macOS — ''sudo dscacheutil -flushcache''.

Specific site blocked by mistake

Sometimes a legitimate site ends up on a blocklist — this happens with smaller news portals, regional banks, or niche services. If the site opens fine after switching to a neutral DNS like 1.1.1.1, the issue is a false positive. Go to adguard.​com/​en/​adguard-​dns/​overview.​html, find the filtering log in your personal dashboard, locate the blocked query and report it as a false positive. Alternatively, add the domain to the allowlist directly in your account settings.

Online banking or payment page won''t load

Payment systems and banking apps are frequent victims of overly broad blocklists. If your bank''s app fails to connect or the payment page throws a network error, check the DNS query log — the culprit is usually a tracking or analytics subdomain that the bank''s frontend depends on. Adding the entire bank domain to exceptions is faster than hunting down individual subdomains.

High latency on DNS resolution

- Pick the server geographically closer to you — AdGuard operates nodes in multiple regions, and routing matters

- On routers, make sure the DNS-over-HTTPS or DNS-over-TLS configuration doesn''t add unnecessary hops through a slow middleware

- Test raw resolution time with ''nslookup -debug example.com 94.140.14.14'' to confirm the delay is on the DNS side, not the site itself

Private DNS profile stops working on Android

Android''s Private DNS mode requires a hostname, not an IP. Use dns.adguard.com as the hostname. If it keeps disconnecting, the cause is usually an aggressive battery optimization policy killing the DNS resolver in the background. Go to battery settings and exclude the system resolver or the browser from optimization. On some Samsung devices you also need to disable ''Adaptive Wi-Fi'' which resets DNS settings on network switches.

Ad-filtering rules break app functionality

Some apps — particularly streaming services and game clients — break when their telemetry endpoints are blocked, showing login errors or refusing to start. If disabling filtering for a specific device in your DNS dashboard fixes the issue, re-enable filtering and use the query log to find which exact domain caused it, then allowlist only that one.