Is OpenDNS down today?

Sites blocked despite correct settings

The most common issue: you''ve configured custom filtering, but legitimate sites keep getting blocked. First, check which category the domain falls into — log into the dashboard, go to Settings → Web Content Filtering, and look at the blocked categories list. If the site is wrongly categorized, add it manually to the whitelist under Settings → Manage Individual Domains.

DNS changes not taking effect

After updating nameservers to 208.67.222.222 and 208.67.220.220, changes can take up to 48 hours to propagate. But if nothing''s changed after a day, the router is likely overriding your settings. Check whether DHCP is pushing the ISP''s DNS instead of yours. Also flush the local DNS cache: on Windows run ipconfig /flushdns, on macOS use sudo dscacheutil -flushcache.

Dashboard login errors

- Clear browser cookies and cached data — stale session tokens cause authentication loops

- Try an incognito window to rule out extension interference

- If you use SSO or a linked account, check that the email matches exactly

- Reset your password only after confirming the email address is correct — support won''t merge duplicate accounts

Stats not updating in the dashboard

If usage graphs show no data or freeze at a specific date, the device''s IP likely changed and no longer matches the registered network. Go to Settings → Networks, check the current IP shown, and compare it with your actual external IP. Use the dynamic IP updater client if your ISP assigns addresses dynamically.

Specific apps can''t connect

- Games and streaming apps sometimes use hardcoded DNS resolvers, bypassing your configuration entirely

- Check the app''s network settings for custom DNS fields and clear them

- Applications like Discord or some smart TV platforms may fail if NXDOMAIN responses are returned instead of standard blocks

- Switching the filtering policy to ''None'' temporarily helps isolate whether the DNS resolver is causing the issue

Slow page loads after switching DNS

High latency on DNS resolution usually means the nearest resolver isn''t being selected automatically. Run nslookup against both 208.67.222.222 and 208.67.220.220 and compare response times. If both are slow from your location, the issue may be with routing at your ISP level — try setting the DNS on the device directly rather than the router to test.