After changing DNS, two people can see different results without either person making a mistake. They may be asking different resolvers that still hold different cached answers.
Identify the record you actually changed
Write down the hostname, record type, old value, new value, and intended purpose. The root domain, www hostname, and mail hostname are separate names. Updating one does not necessarily update the others.
Confirm which nameservers are authoritative. Editing a zone at a provider that is no longer authoritative will not change the public answer.
Understand the cache window
TTL tells a resolver how long it may retain an answer. Reducing TTL immediately before a change cannot remove copies already cached under the previous TTL. Plan the reduction in advance when a shorter transition matters.
Negative answers can also be cached. A recently created hostname may therefore remain unavailable to a resolver that previously received an answer saying it did not exist.
Check the right layers
Compare an authoritative response with results from your usual resolver. If the authoritative answer is wrong, fix the zone. If it is correct but a recursive resolver still returns the previous answer, investigate caching before repeatedly editing records.
If DNS points to the correct server but the page remains wrong, check the web server hostname configuration, application routing, CDN cache, and TLS certificate.
Preserve email service
Website migration does not require changing every DNS record. Keep existing mail records unless email is also moving. Export the original zone and prepare a rollback plan before modifying nameservers.
Published for Alif Host. Always confirm the exact DNS requirements with the service receiving the traffic.
