Insights /Network, remote access and firewall

DNS returns Server Failure or SERVFAIL: checking forwarders, firewall port 53 and cache

SERVFAIL means the resolver could not complete the query. Check authoritative data, forwarders, TCP/UDP 53, DNSSEC, timeouts and cache in sequence.

DNS returns Server Failure or SERVFAIL: checking forwarders, firewall port 53 and cache
Key assessment

Establish a factual baseline with “authoritative-zone state” and “forwarder reachability and timeout”, then move to “TCP/UDP 53 firewall policy”. Use routing, policy, session state and real application traffic as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking authoritative-zone state, forwarder reachability and timeout and TCP/UDP 53 firewall policy independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · authoritative-zone stateChecking authoritative-zone state helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of authoritative-zone state. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
02 · forwarder reachability and timeoutChecking forwarder reachability and timeout helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of forwarder reachability and timeout. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
03 · TCP/UDP 53 firewall policyChecking TCP/UDP 53 firewall policy helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of TCP/UDP 53 firewall policy. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
04 · recursion and root-hint configurationChecking recursion and root-hint configuration helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of recursion and root-hint configuration. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
05 · DNSSEC/EDNS compatibilityChecking DNSSEC/EDNS compatibility helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of DNSSEC/EDNS compatibility. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
06 · negative cache and server cacheChecking negative cache and server cache helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of negative cache and server cache. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
Read-only examples
nslookup example.com 192.0.2.53
Resolve-DnsName example.com -Server 192.0.2.53

Investigation and change sequence

  1. Capture a baseline for authoritative-zone state and forwarder reachability and timeout and compare it with a known-good system.
  2. Correlate evidence from TCP/UDP 53 firewall policy and recursion and root-hint configuration to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to DNSSEC/EDNS compatibility, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check negative cache and server cache and the real business workflow. Verify end-to-end business access, return routing and error logs, with a defined rollback check.

Validation and rollback evidence

  • Verify end-to-end business access, return routing and error logs, with a defined rollback check.
  • Recheck DNSSEC/EDNS compatibility and negative cache and server cache against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming authoritative-zone state is sufficient while overlooking forwarder reachability and timeout and dependent checks.
  • Changing several settings before preserving the original evidence for TCP/UDP 53 firewall policy.
  • A successful port probe is not proof of application functionality; do not broaden access rules blindly.

Common questions and acceptance criteria

What should be checked first?

Begin with authoritative-zone state and forwarder reachability and timeout. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Verify end-to-end business access, return routing and error logs, with a defined rollback check.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousDesigning DNS conditional forwarders for an isolated network that must resolve only vendor domainsNextWith two enterprise DNS servers, must forwarders, cache and root hints be identical?

Need an assessment based on the actual environment?