Authoritative DNS vs Recursive DNS

Short Description

Compares source-of-truth publishing versus client-facing resolution and caching responsibilities.

Clarifies where outages originate and which telemetry to prioritize.

Authoritative systems host zone data while recursive systems fetch/cache it for users.

Compare authoritative direct answers with recursive resolver outcomes.

Instrument both layers and assign clear ownership boundaries.

An issue blamed on authority was actually a recursive cache-poisoning incident.

Layered findings across authority and resolver perspectives.

Relevant checks: Delegation integrity, resolver consistency, DNSSEC health, and suspicious record-pattern checks.
Severity mapping: Informational, medium/high, or critical based on exploitability and user impact.
Score impact: Reliability and security scoring dimensions are reduced according to blast radius.
Related findings users will see: NS drift, validation failure, orphaned CNAMEs, wildcard exposure, and policy misconfiguration alerts.

Verify behavior from at least two public resolvers and one resolver inside your own network before making changes.
Make one change at a time, capture before/after query output, and wait for TTL windows to clear so you can confirm impact.
Document the root cause and the final fix in your runbook to shorten future incidents.