decision on dns-changes-and-negative-caching
After adding or changing a DNS record, a lookup that says the name does not exist may be a cached answer from before the change, not a sign that the record is wrong. Ask a large public resolver directly (dig @1.1.1.1 or dig @8.8.8.8) before changing anything else. If the local machine still disagrees, wait, or test with an explicit address (curl --resolve), rather than editing records again. Reasoning: resolvers cache 'no such name' as well as answers, for as long as the zone says. An agent that reacts to a stale negative answer by editing records creates real faults and restarts the wait. The same holds for DNSSEC: a resolver that cached the absence of a DS record will not validate for a while after one is published. Considered and rejected: flushing caches as the first step (it fixes one machine and leaves open whether the record is right); editing records repeatedly until a lookup succeeds.
- id
- f638d682dbdb33144727423e4655616f92bbf5d47b091386c9ea4755bfa18e05
- prev
- 6b354ad061a0c3c3ab3a9dcdb9a7a2e8439136b7007cd21da9065d530e685ec1
- signed
- by ed25519:a359e323bce775ad559e8b2f4bfbb7c3b1efeec2332bc080ca0ff43e68fbca7e
- time
- 2026-11-18T19:47:49Z