Authoritative vs recursive DNS

The distinction between authoritative and recursive DNS becomes clear along the stub resolver → recursive resolver → delegation → authoritative nameserver path. A recursive resolver can answer from cache, so a user response is not necessarily fetched directly from the authoritative server. TTL, record type and response code explain where the result came from and how long it can remain usable.

How to check the DNS result

Check the name and query type first, then the authoritative answer, then the chosen recursive resolver. NXDOMAIN, SERVFAIL, REFUSED and timeout represent different conditions. After a DNS change, compare authoritative data with several resolvers; clearing a local cache helps only when the stale answer is actually local.

The detail that matters

Ask the authoritative server directly before blaming a recursive resolver. If authoritative data is correct but a resolver differs, compare TTL/cache age; if delegation is wrong, changing the record inside the zone may not repair the path. You can repeat the DNS check with 2ip DNS response check.