procedure / Domains & DNS
Change a DNS record safely
A safe DNS record change begins by locating the actually delegated authoritative zone, checking your authorization and preserving the complete RRset you intend to replace. Prepare the new name, type, class, values and TTL, as well as a scoped rollback, before mutation. Verify the authoritative answer first and then observe particular recursive resolvers; cached answers can remain different without the authoritative edit being wrong. This is an operational workflow and an explanatory cache model, not a promise of a worldwide cutover time.
What it means
DNS editing and DNS cache expiry answer different questions. The authoritative zone determines what the intended source now publishes; resolvers may reuse a previously saved answer until its eligible lifetime ends. An authorized change needs both a precise source-of-truth edit and a separate read-only observation plan. A provider “Saved” message only establishes a local control-plane action, not that the delegated authoritative servers and visitors agree.
Try it
DNS change and a previously cached answer
SimulationStarting from Reset, select the `old_cached` preset. It keeps Prior cache state at `positive_old`, sets Elapsed seconds to `120`, and sets Synthetic authoritative change to `applied`.
The prior positive-cache scenario, original 300-second cache lifetime, and example addresses remain fixed. Only elapsed time and the synthetic authoritative-change setting change from baseline. No real DNS data or resolver is changed.
Selected scenario: baseline
Old positive cache usable
- Authoritative address
- 192.0.2.10
- Cached answer
- 192.0.2.10
- Remaining lifetime (seconds)
- 300
- Next query
- not observed
The previously cached answer remains usable for 300 seconds in this fixed timeline. No synthetic authoritative change has been applied; the authoritative and cached values still match.
Local simplified timeline; never a global cutover prediction.
Recent valid actions
The last ten valid changes in this local example. Reset clears this history.
No changes recorded.
Select Reset to return to the baseline preset: Prior cache state positive_old, Elapsed seconds 0, and Synthetic authoritative change not_applied. Reset replaces temporary input and scenario selections and clears local errors, history, and comparison. It does not change whether FAQ or About this model disclosures are open, and it changes no real server or external network.
About this model
This is a Simulation of one previously cached DNS answer, not a live DNS check. At the baseline, the authoritative and cached addresses are both 192.0.2.10, the old positive answer has 300 seconds remaining, and the next query is not observed. The controls let you choose the prior cache state, enter elapsed seconds, and apply a synthetic authoritative change. The model cannot edit a zone, inspect a resolver, authenticate an answer with DNSSEC, or establish that a real service works.
How it works
An authoritative server supplies the zone's current data, while a recursive resolver may already hold an earlier answer. Updating the authoritative RRset after approval changes the source data; it does not replace copies already cached elsewhere. Those earlier copies can remain usable for their remaining ordinary TTL. RFC2181 §5.2 requires the records within one RRset to have the same TTL.
Absence can be cached too. Eligible NXDOMAIN and NODATA responses use a negative lifetime initially determined by the smaller of the SOA record's TTL and SOA.MINIMUM, as described in RFC2308 §§3 and 5. That mechanism is different from caching a positive address and different from caching a resolution failure.
The important contrast is a correct RRset published in the wrong, nondelegated zone. Even an extremely short TTL on that unused source cannot make recursive resolvers consult it. Another contrast is an eligible negative response stored before a name was created: its lifetime is determined by the earlier SOA-based negative-answer rule, not by the new positive record’s TTL. A timeout or SERVFAIL is not an authenticated absence; separate failure caching applies. Keep these explanations conditional on the observation actually obtained.
A worked example
For the separate negative-cache example, the model fixes the SOA TTL at 150 seconds and SOA.MINIMUM at 120 seconds. The initial negative lifetime is therefore min(150, 120) = 120 seconds. The negative preset evaluates that cached absence 50 seconds later, with the synthetic authoritative change applied, leaving 120 − 50 = 70 seconds of cached absence. This illustrates why adding a record need not immediately displace an earlier eligible negative answer. These SOA values are fixed example assumptions, not editable controls, and the next successful response is not established.
What changes the conclusion
An expired cache entry is not proof of a successful update. In the old_expired preset, 300 seconds have elapsed, the synthetic authoritative address is 192.0.2.20, and the old cached answer is no longer usable in the ordinary TTL model. The next query is still not observed. It could fail or return an answer that must be checked; the simulation has not demonstrated successful resolution.
In practice
Use this procedure only in the authoritative DNS provider's environment for the intended zone, with an account role authorized to make the approved change. Provider controls and rollback steps differ; this simulation is a rehearsal, not a provider-specific editing guide.
The workflow below is WebsiteHosting.com's operating rule for this procedure, not a DNS protocol requirement. Begin read-only. Confirm the authoritative nameservers and active zone, then capture all affected RRsets, their values, and TTLs. Preserve MX and TXT records and any other records outside the approved change. Write down the expected complete replacement RRset and the exact values needed to restore the original. An RRset groups records with the same name, class, and type; its members must have consistent TTLs.
Before editing, expect the captured source, zone, and records to match the approved plan. STOP if the source or zone is unexpected, the name or type differs, the before-state is incomplete, permissions are unclear, or the rollback plan is missing. Resolve the discrepancy and obtain approval rather than guessing.
After approval, change only the specified RRset and its approved TTL using the provider's documented process. Verify that the authoritative answer matches the intended complete set and that unrelated records remain unchanged. Then compare recursive resolver answers, recording which resolver answered, when, and any relevant TTL. A recursive mismatch may reflect a prior cache entry; it is not by itself proof that the authoritative edit failed.
If the change meets your documented rollback criteria, restore only the approved before-state through the provider's process. Verify the restored authoritative data and compare resolver observations again. Restoring authoritative data does not instantly remove cached answers from the attempted change, and a synthetic retest does not verify the real service.
A synthetic cross-check should include the old and new complete RRsets, not only one address, and should record whether unrelated MX/TXT and delegation data stayed unchanged. The STOP condition applies before saving: if the zone, permissions, previous values or rollback path do not match the approved scope, do not improvise a broader edit. After rollback, verify the restored authoritative values independently; previously cached new answers can still remain until their own lifetimes expire.
Limits and unknowns
The elapsed-time model assumes a known starting cache lifetime without intervening refreshes or resolver-specific TTL caps. Actual resolver contents, refresh history, and local policies are unknown unless separately observed. The authoritative value in the example is assumed, not obtained from a network query or cryptographically authenticated.
Keep three states separate: an eligible negative answer reports absence; a resolution failure does not establish absence; and “next query not observed” means no next-query outcome has been evaluated. For eligible NXDOMAIN or NODATA, the SOA-based negative lifetime applies. Timeouts and SERVFAIL use separate failure-caching rules under RFC9520.
Ordinary TTL expiry is also not a complete description of every resolver. RFC8767 permits scoped serve-stale behavior when refreshing fails. This model does not simulate that behavior and cannot predict a global propagation deadline.
What to take away
A DNS change is ready to assess only after the specific delegated authority, complete intended RRset and permission/rollback scope are known. First verify the actual authoritative data; then identify each resolver, question and observation time. Treat a cached mismatch, authenticated negative answer and unavailable next response differently. Waiting may explain one old cache entry, but only new evidence can establish the outcome of the next real lookup.
Frequently asked questions
Editorial questions, supported by the references below.
Can SERVFAIL or a timeout establish that a DNS name is absent?
No. SERVFAIL and timeouts indicate resolution failure, not an authoritative NXDOMAIN answer. RFC 9520 addresses failure caching separately from eligible SOA-derived negative answers. Record the resolver, exact question, time and relevant failure evidence before inferring anything about existence.
When can a newly added record remain invisible because of earlier NXDOMAIN?
A resolver may have cached an eligible NXDOMAIN or NODATA response before the name or type was added. Its remaining negative lifetime can outlast the authoritative change. In the synthetic example, min(SOA TTL 150, SOA.MINIMUM 120) gives 120 seconds initially and 70 remain after 50 seconds. This does not guarantee the next query will succeed.
What does no prior cached entry tell you about the next resolver answer?
It means only that this particular model has no earlier cache item to reuse. No real next query has been observed. The response might be new data, a negative answer, a failure or something else; obtain evidence from the named resolver instead of treating “no prior cache” as confirmed success.
When should an authorized DNS change stop before mutation?
Under the project’s authorized-change workflow, stop before editing if the actual delegated zone, account permission, complete previous RRset, intended name/type or rollback plan does not match the approved scope. Clarify the discrepancy and authorize any changed scope first; a DNS TTL rule cannot grant permission to modify mail or delegation.
Sources & model boundaries
The interactive is a local educational simulation, not a live check. Protocol references and WebsiteHosting.com operating rules are identified separately.
- DNS03 — Protocol or bounded model reference
The RRs within one RRset MUST have the same TTL (RFC2181 §5.2). An authoritative RRset change can coexist with a prior cached response; serve-stale behavior is a separate exception and must not be silently assumed.
HQ reviewed targeted core claim; no complete current errata/updates audit or all-sentence factcheck
Recorded targeted check: .
- DNS04 — Protocol or bounded model reference
Eligible NXDOMAIN/NODATA answers use the SOA-based negative TTL, initially the minimum of SOA TTL and SOA.MINIMUM. Resolution failures are cached under separate RFC9520 rules; timeout or SERVFAIL is not proof of authoritative absence and does not use this fixture's SOA negative-answer branch.
HQ reviewed targeted core claim; no complete current errata/updates audit or all-sentence factcheck
Recorded targeted check: .
- POLICY01 — Project operating rule
WebsiteHosting.com's operating rule for an authorized DNS change is to establish the intended zone, exact RRset, permissions, complete before-state and rollback plan before a change. Stop if these do not match the approved scope; clarify and reauthorize a changed scope instead of improvising. This is the project's safety workflow, not a DNS TTL or cache-expiry rule.
Project operational policy for this educational procedure. It does not establish DNS protocol behavior, provider-specific controls, legal authority, successful execution, cache invalidation or a universal operational standard.
- CONTENT 2.4 — ## 11. Безопасность, доверие и поддержание актуальности
Document SHA256:
41fb2793a3841f80ec1dd3b11d95a3ed24a86aa53719720c7a7f77f0b74d599b - WORKFLOW 1.8 — ## 2. Задание — не больше одной страницы
Document SHA256:
80aae89feec666742956774b6c662e28a980075a2f5b111b77d3f117deee0d85 - Content Quality Guideline v1/R4 — ## 4. Contracts by page type
Document SHA256:
5288e52291026f2f529277355b6cc9d363f71becd5756ae6ccfcdc1ae955dcad
Recorded targeted check: .
- CONTENT 2.4 — ## 11. Безопасность, доверие и поддержание актуальности
Report an issue. Include the article URL and ID, not passwords or access keys.