RTFM · Troubleshooting
DNS problems
Names fail while IPs work: work through clients, caches, recursion and delegation, each with a command that isolates it.

Isolate the failing layer
DNS failure lives at exactly one of four layers; query each explicitly.
# Direct authoritative answer?
drill @198.51.100.53 example.net SOA
# Our configured resolver answers?
drill example.net
# Full chain visible?
drill -T example.net
cat /etc/resolv.confresolv.conf is wrong or rewritten
Hand-edited resolv.conf overwritten at boot means a DHCP client or provisioning script owns it. Fix the source, not the file.
Some client configurations rewrite resolv.conf on every lease renewal. Configure search domains and nameservers centrally, otherwise edits evaporate silently.
Running our own DNS?
dnsDragon deployments add their own failure modes: zone transfer failures, DNSSEC signature expiry, and firewall rules blocking UDP/53 inbound. The dedicated chapters cover verification drills for each.
Did we miss something?
If this page left something unanswered, found an error, or there is another subject you would like documented, tell us. Saphira’s documentation grows from real problems people need to solve.
Send feedback or request a new section →
Prefer not to do it yourself?
Everything needed to do the work yourself is documented here and remains free — we charge for human time, not for withholding knowledge. Sometimes the missing resource is simply time. The same people who build Saphira can provide paid professional help with implementation, migration, troubleshooting and administration.