You create a new subdomain. The management interface shows the record, a colleague can reach the site, but your computer still reports NXDOMAIN. Has the change failed? Not necessarily. A resolver can also remember that a name did not exist before. This stored negative answer is a state in its own right.
Cloudflare’s DNS troubleshooting guide, updated on 21 October 2026, describes exactly this case. This is a current technical explanation, not the launch of a new DNS product. The distinction is worth making because several completely different stores disappear under the everyday word “cache”: DNS answers, browser content and cached web files.
The earlier non-existence may still be stored
A recursive resolver looks up the name on your behalf. If it has previously received a negative answer, it can reuse that answer for a limited time. If the record is created on the authoritative nameserver in the meantime, the resolver does not necessarily find out at the same moment.
The new TTL of the A record you have just created does not retroactively shorten this existing negative state. For negative caching, the zone’s SOA information plays a role. RFC2308 describes the starting value as the smaller of the SOA TTL and SOA.MINIMUM. The time actually remaining for a stored answer is something different again.
Our own worked example uses only invented numbers: a negative entry may initially be valid for 300 seconds. After 120 seconds, the real DNS record is created. A resolver could then still have 180 seconds of its old answer left. This illustrates the timing relationship; it is not a measured duration for Cloudflare or your domain.
Two read-only queries separate source and cache
The first question is: what does the responsible authoritative nameserver say? The second: what does the recursive resolver that your device actually uses say? Different answers can narrow down the fault. They do not automatically prove negative caching; typos or incorrect delegation must also be ruled out.
dig @YOUR-AUTHORITATIVE-NAMESERVER neu.example.com A
dig @YOUR-RECURSIVE-RESOLVER neu.example.com A
dig @YOUR-RECURSIVE-RESOLVER neu.example.com A +noall +authorityReplace the placeholders with the servers you have actually identified. The commands are read-only templates and were not run here. Look at the response code, name, record type and, where present, SOA details together. An answer for a similarly spelt host would not be a suitable comparison.
Also record the time and the resolver used. Otherwise you may be comparing different paths without noticing. Clearing the local DNS cache does not automatically remove the stored answer of an upstream resolver. That is exactly why restarting the browser can miss the state you are observing.
DNS and CDN answer different questions
DNS helps resolve a name. A CDN cache, by contrast, keeps certain HTTP content ready. Purging cached images or stylesheets does not tell a DNS resolver that a previously unknown name now exists. The measure then simply does not match the layer where the problem lies.
Cloudflare’s getting-started guide for Cache, last updated on 12 October 2026, also describes the difference between proxied and DNS-only: content from a DNS-only host does not pass through the Cloudflare cache merely because its DNS is managed there. An existing DNS record is therefore no evidence that content is actively being cached.
From DomainStudio to the actual answer
In KENJTEC DomainStudio ai, you can manage your own DNS records with type, target and TTL. The implemented route uses Cloudflare for zone management. After a change, you should still judge resolution by the actual DNS answers; “saved” and “already visible at every resolver” are different statements.
Waiting times therefore cannot be replaced by a blanket promise of success. First check the spelling, the responsible nameservers and the authoritative answer. Only then is the remaining cache time a useful explanation. This turns “DNS just takes time” into a traceable diagnosis in which every observation belongs to the right technical layer.
Sources and status
Research and documentation as of 25 October 2026. General DNS issues · Get started with Cache · RFC2308 — Negative Caching of DNS Queries.
