Negative caching
Resolvers also cache "doesn't exist" answers:
- NXDOMAIN — the name doesn't exist.
- NODATA — the name exists, but has no record of the requested type.
How long? The negative TTL, defined by the zone's SOA record: the smaller of the SOA record's own TTL and its minimum field (the last number in the SOA) — RFC 2308.
example.com. 900 IN SOA ns-1.awsdns-01.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
In this (Route 53's default) SOA, the minimum field is 86400 but the SOA record's TTL is 900, so negatives are cached for 900 seconds (15 minutes).
The classic trap: someone runs curl new-api.example.com before the record is created (or a deployment pipeline checks too early). The resolver caches NXDOMAIN for 15 minutes, and "the new record doesn't work" even though it's correct in Route 53. Fixes: wait out the negative TTL, flush the resolvers you control, and avoid querying names before creating them. You can lower the negative TTL by editing the SOA record in Route 53.