Skip to main content

SecuraWall.com

Email security and continuity

Explore

Troubleshooting · Cybersecurity

DNSSEC SERVFAIL Troubleshooting: DS, DNSKEY, RRSIG and Time

A DNSSEC validator builds a chain from a root trust anchor through the parent DS record, the child DNSKEY and the RRSIG over the requested RRset. A complete chain yields secure data. A…

Technical review:

Architecture and operating model

A DNSSEC validator builds a chain from a root trust anchor through the parent DS record, the child DNSKEY and the RRSIG over the requested RRset. A complete chain yields secure data. A signed delegation with a key, signature or denial mismatch becomes bogus, and the validator normally returns SERVFAIL. SERVFAIL alone is not proof of DNSSEC failure because timeouts and authoritative errors use the same response code.

Compare the same name with validation enabled and with the Checking Disabled bit. If normal `dig +dnssec` returns SERVFAIL while `dig +cd +dnssec` returns data, validation is a strong suspect. Keep AD, CD and DO distinct: DO requests DNSSEC records, CD asks the recursive server not to validate, and AD says the server authenticated the response. An RFC 8914 Extended DNS Error can narrow the cause, but its text is not authenticated evidence by itself.

Walk the chain from parent to child. The parent DS digest must match the published KSK DNSKEY, including algorithm and digest type. DNSKEY and data RRsets need RRSIG records valid at the resolver's current time. Clock skew, expired signatures, premature key removal, missing DS data, fragmented UDP responses or blocked TCP port 53 can all break validation. Query every authoritative server directly to compare serials and keys.

Disabling validation globally hides the fault and removes protection for unrelated zones. Identify the affected name, failed link and change time first. Repair DS and DNSKEY rollover when you own the zone. For a third-party zone, consider a negative trust anchor only with an explicit scope, lifetime and removal condition. Remember that validation-failure caches and different network paths can delay a consistent recovery.

  1. 1Client query and SERVFAIL
  2. 2Validating resolver log and EDE
  3. 3DS-DNSKEY-RRSIG chain
  4. 4Authoritative repair and cache recovery
Treat SERVFAIL as a symptom; use control-bit comparison and chain evidence to isolate a validation failure.

Design parameters

Chain scope
Capture DS, DNSKEY and RRSIG evidence from the root-side delegation to the queried name.
Signature time
Compare RRSIG inception and expiration with the resolver's trusted UTC clock.
Transport path
Test EDNS size, fragmentation, UDP and TCP port 53 with firewall counters.
Authoritative consistency
Query each NS address directly and compare SOA serials and key sets.
Cache lifetime
Document failure caching, TTLs and the expected recovery window after correction.

Worked example

If normal validation returns SERVFAIL and `+cd` returns NOERROR, inspect the resolver log and any EDE code. Fetch the parent DS and child DNSKEY, then use `delv` to show where the chain stops.

If an RRSIG starts at 10:00 UTC but the resolver clock reads 09:54, correct keys still appear premature. Repair the time source, then verify the signing cycle, every authoritative serial and two independent validating resolvers.

Example commands: replace lab values and confirm permissions and software versions before use.

dig +dnssec www.example.com A
dig +dnssec +cd www.example.com A
dig +dnssec +tcp www.example.com A
dig DS example.com
dig DNSKEY example.com +multiline
delv www.example.com A

Troubleshooting

ObservationLikely cause / distinctionVerification
Only one resolver failsIts cache, trust anchor or network path may be unique.Compare `+cd`, TCP and another validator, then inspect clock and logs.
DS exists but DNSKEY is missingThe child keys may be absent or a large answer may not traverse the path.Query every authoritative server over UDP and TCP and inspect EDNS and firewall counters.
SERVFAIL persists after repairA failure cache may remain, or one authoritative server may still serve old data.Compare SOA serials, failure-cache lifetime and cache-flush scope.

Acceptance checks

  1. Record normal, `+cd` and `+tcp` queries with one timestamp.
  2. Identify the EDE code and failing RRset in validator logs.
  3. Match the parent DS to child DNSKEY algorithm and digest.
  4. Compare RRSIG times with trusted UTC.
  5. Verify SOA serial and key set on every authoritative server.
  6. Obtain an AD-marked answer from two independent validators.

Related concepts

DNS caching and dependencies

DNS results depend on client and recursive-resolver caches as well as authoritative data. Changing a TTL does not retroactively shorten already cached answers. A/AAAA, CNAME, MX and TXT records serve different purposes. Test internal and external views separately; split DNS may intentionally return different results. Record resolver, response type, TTL and query time when troubleshooting. Successful access by IP address alone does not prove correct DNS configuration.

Trust boundary and failure domain

A trust boundary separates components governed by different access decisions; a failure domain groups resources that one event can affect together. Two VLANs do not create a strong trust boundary when routing between them is unrestricted. Backups in different folders still share a failure domain if one administrator can delete both. Assess physical location, identity provider, management account, network path and power source separately. Test which access paths and recovery options remain available when a component is lost.

Telemetry and time correlation

Telemetry combines logs, metrics and events that explain system behavior. A log describes an event, a metric shows behavior over time, and a distributed trace follows a request across components. Clock differences can make one event appear to occur at several times. Use synchronized clocks, reliable source identifiers and consistent time-zone handling. Alarm design should consider duration and user impact alongside thresholds. Monitor gaps in collection separately: absence of logs must not be interpreted as absence of incidents.

Availability versus recovery

High availability aims to keep service running through specified failures with a short interruption; backup recovers lost or corrupted data from an earlier point. A cluster can replicate an accidental deletion to another node. HA therefore does not replace backup. Consider DNS, identity, network, storage and power dependencies together. Successful node failover is insufficient by itself: measure user sessions, application writes and external integrations after the transition as well.

Application consistency

A bootable copy does not prove application-data consistency. Operating-system caches, database logs and write ordering across disks or services affect the result. A crash-consistent copy resembles recovery after an unexpected shutdown; an application-consistent copy follows supported application preparation and write coordination. Validate transaction integrity, relationships between records and application behavior after recovery, rather than only counting files. Confirm backup integration, application version and reported errors before assuming that consistency was achieved.

Version and support lifecycle

Installability does not prove production support. Review the compatibility chain across OS, application, drivers, extensions and management tools. Update plans should record version, support end, restart needs and rollback methods. A test environment that does not reflect production can produce misleading results. Validate service health and existing workflows after a change, not just version numbers. Remember that pinning a version can also prevent future security fixes.

Primary documentation

Prepared by the Doz Teknoloji technical team using the primary references below. Calculations and lab scenarios state their assumptions; validate the applicable product version before rollout.

Knowledge Center

Enterprise IT Product Sales, Licensing and Deployment
Enterprise IT Project & Solution Scenarios
View all related content
Text on WhatsApp
Copied!