OpenDNS not working in India today?

Sites blocked despite being whitelisted

If a domain you added to the whitelist still gets blocked, the most likely culprit is DNS caching. Your device or router may still be serving the old blocked response. Flush the local DNS cache: on Windows run ''ipconfig /flushdns'', on macOS use ''sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder''. Then clear the browser cache and try again. Also double-check that the domain is entered without typos and without the ''http://'' prefix — the dashboard expects bare domains like ''example.com''.

Dashboard login not working

If you can''t get into the account panel, first confirm you''re hitting the correct URL: ''login.opendns.com''. A common mistake is saving an old redirect in bookmarks. Try an incognito window to rule out cookie conflicts. If the password reset email isn''t arriving, check the spam folder and make sure the address on the account is still active — the system sends from ''@opendns.com'' domains.

DNS resolution fails for specific sites

Some applications and games stop resolving hostnames while general browsing works fine. This usually means the app is using a hardcoded DNS server instead of the system one, bypassing your settings entirely. Check the app''s network configuration and force it to use the system resolver. Also verify that your router is actually forwarding queries to 208.67.222.222 and 208.67.220.220 — not to your ISP''s servers.

Stats and logs not updating

The usage graph on the dashboard updates with a delay of up to three minutes. If stats haven''t appeared for over 30 minutes:

- Confirm your external IP matches what''s shown under Settings → Dynamic IP.

- Check that the dynamic IP updater client is running and not blocked by a firewall.

- Make sure at least one device on the network is actually routing DNS through the service, not through a secondary resolver.

High DNS lookup latency

If pages feel sluggish and traceroute shows elevated times specifically on DNS steps, the issue is often a misconfigured secondary DNS. Some routers fall back to a slow ISP resolver if the primary doesn''t respond within a tight timeout. Set both primary and secondary to OpenDNS addresses explicitly, and disable any ''DNS acceleration'' or ''SmartDNS'' feature your router vendor may have enabled by default — these often interfere with external resolvers.