Enhanced nextdns-doctor script with public DNS checksPublic

Agent

Model

GPT-5.5

Started

Apr 29, 6:20 AM

Messages71

Downloads5

Summary

Closed, Completed

Edit
Added dig checks for Cloudflare and Google DNS resolvers.
Edit
Edit
Improved output formatting with clearer headers and status markers.
Edit
Edit
Modified script to conditionally show 'Common fixes' only on failures.
Edit
Verify
Validated script syntax and output behavior.
Verify

I want to modify /usr/local/bin/nextdns-doctor script to also check if dig works when using cloudflare or Google DNS as the resolver. This can help identify issues where nextdns is specifically unable to resolve domains. Let me know if this check is already covered.

Done.

This check was not already covered directly. The script had:

dig @127.0.0.1 and dig @::1 — checks NextDNS local daemon
system resolver checks via dscacheutil
HTTPS reachability to NextDNS upstream

But it did not test public DNS resolvers like Cloudflare or Google directly.

I added a new section:

It now checks:

Behavior:

PASS if public DNS works
WARN if public DNS fails, since some networks intentionally block external DNS
Adds a note that if public DNS works but NextDNS loopback fails, the issue is likely NextDNS-specific

I also ran:

and syntax is OK.

can you also make the ouput look cleaner

resume

Done. I cleaned up the output formatting in /usr/local/bin/nextdns-doctor.

Changes include:

Cleaner section headers: ▸ Section name
Clear status markers: ✓ PASS, ! WARN, ✗ FAIL
More compact header with host/time
Cleaner dig output — shows one IP plus (+N more) instead of dumping all answers
Cleaner public DNS checks for Cloudflare/Google
Cleaner system resolver and HTTPS messages
Aligned config output
Recent logs are now deduplicated, shortened, and noisy macOS security lines are filtered out
Summary now reads like:

I also ran:

and executed the script to verify the output looks good.

Only show the common fixes section if something has failed

Done.

Common fixes now only prints when FAIL > 0.

I also removed a stray Timestamp... log header from the recent logs output while validating the script.

Syntax check passes: