Why Does DNS Still Show an Old Result After a Change? Separating TTL from Negative Caching
After a DNS change, the result may be an old record value, NXDOMAIN, or NODATA. Learn what each response means and why it may remain cached.
DOMAINQ BLOG
Guides to domain names, DNS records and connecting your services.
Start with what you need.
After a DNS change, the result may be an old record value, NXDOMAIN, or NODATA. Learn what each response means and why it may remain cached.
Start interpreting an RDAP result with the HTTP status code and JSON structure before reading object fields. This helps distinguish successful queries, unsupported query types, and invalid requests.
The right RDAP starting point depends on the target of your question: a domain, one nameserver, or a set of search results.
A field missing from an RDAP response does not by itself mean that no record exists. Review data scope, authorization, and the queried object type together.
More than one TXT record can exist under the same DNS-01 name. But as old records accumulate, the DNS response can grow and Let’s Encrypt may reject it.
RDAP treats a domain object as a DNS name and a point of delegation. Learn to read ldhName, v4, and v6 in nameserver objects carefully.
DNSSEC validation does not rely on one record alone. A trust anchor starts a chain of DNSKEY and DS links leading to signed DNS data.
In an RDAP response, status describes the registered object’s state, while events describe occurred or future-dated events. Keeping them separate helps you read registration data carefully.
Different DNS results after a change can arise from the difference between authoritative information and information retained by the DNS service reached by a query.