Is NextDNS down today?

Sites blocked despite whitelist

If a domain you added to the allowlist still gets blocked, the issue is usually caching. Flush the DNS cache on your device: on Windows run ipconfig /flushdns, on macOS use sudo dscacheutil -flushcache. Then check the Logs tab in the dashboard — it shows in real time whether the query is reaching NextDNS at all and what rule is matching it. Sometimes a wildcard blocklist entry overrides your allowlist; add the domain with a leading dot (e.g. .example.com) to cover subdomains too.

DNS queries not reaching NextDNS

Open nextdns.io/test — if it says you''re not using NextDNS, the configuration isn''t applied. Common causes:

- The wrong profile ID is set in the app or system settings

- Another DNS is hardcoded in the router and overrides device-level settings

- The CLI client isn''t running: check with nextdns status

- On iOS, the configuration profile got removed after an OS update — reinstall it from the dashboard

Online banking or payment site broken

Financial services often break when CNAME cloaking protection or the "Block Disguised Third-Party Trackers" feature is on. Go to Settings → Privacy and temporarily disable that option, then retry. If it helps, add the bank''s domain to the allowlist rather than keeping the feature off globally. Also check that "AI-Generated Threat Intelligence" isn''t flagging the bank''s IP ranges — the Logs tab will show a THREAT_INTELLIGENCE block reason if so.

High latency on DNS resolution

NextDNS routes queries to the nearest PoP, but if your ISP''s routing is suboptimal, you might land on a distant server. Check which endpoint you''re hitting at nextdns.io/test — it shows the server location. Switching from DNS-over-HTTPS to DNS-over-TLS (or vice versa) sometimes picks a better route. If you use the CLI, try nextdns config set -report-client-info to help the service pick the closest resolver.

Dashboard logs not updating

- Make sure logging is enabled in Settings → Logs — it''s off by default for privacy

- Log retention is limited; older entries are dropped automatically

- If the live feed freezes, hard-refresh the page (Ctrl+Shift+R) — it''s a WebSocket stream that drops on idle connections

- Ad blockers in your browser can interfere with the dashboard''s real-time updates; whitelist app.nextdns.io

App login fails or session drops

If you can''t log in, first check that your browser allows third-party cookies — the auth flow relies on them. Clearing site data for nextdns.io usually fixes persistent session errors. The CLI uses a separate API key; regenerate it in Account → API and run nextdns login again if commands return 401 errors.