Cyclone Hosting practical guide: DNS updates appear inconsistent because resolvers cache information for different lengths of time.
DNS Connects Names To Services
DNS translates names such as example.com into technical destinations such as IP addresses and mail servers. Without DNS, visitors would need to remember server addresses.
Common Record Types
- A: points a hostname to an IPv4 address.
- AAAA: points to an IPv6 address.
- CNAME: aliases one hostname to another.
- MX: identifies mail servers.
- TXT: stores verification and email-policy information.
- NS: identifies authoritative nameservers.
Why Changes Are Not Instant Everywhere
Resolvers cache DNS answers to reduce load and improve speed. The TTL value tells resolvers how long they may keep a cached answer. Until the cache expires, some visitors may continue seeing the old destination.
Propagation Is Really Cache Expiration
People often call this delay propagation, but the change does not slowly travel in one direction. Different resolvers refresh at different times.
Nameserver Changes Can Take Longer
Changing authoritative nameservers affects how the entire DNS zone is located. Existing delegation information and cached records may remain active for a while.
Plan Changes Carefully
Lowering TTL values before a migration can reduce the time old records remain cached. Do this early enough for the previous TTL to expire before the planned change.
How To Check DNS
Use DNS lookup tools to compare A, MX, TXT, and NS records. Remember that your local computer may show a cached result even when another resolver has updated.
Propagation Is Usually Cache Expiration
There is no single copy of DNS that moves across the internet in one wave. The authoritative nameservers publish the current record. Recursive resolvers used by internet providers, offices, phones, and public DNS services cache that answer for its time to live, or TTL. After a record changes, a resolver may continue returning its cached answer until that timer expires.
This explains why one device can reach the new server while another still reaches the old one. It does not automatically mean the change failed. It means the two devices may be asking different resolvers with different cached data.
Nameserver Changes And Record Changes Are Different
Changing an A record inside the current authoritative zone keeps the same DNS provider and replaces one answer. Changing nameservers delegates the entire zone to a different provider. A nameserver change is broader because the new zone must contain every required web, mail, verification, and service record. Missing MX or TXT records can interrupt mail even if the website works.
| Observation | What it suggests | Next check |
|---|---|---|
| Authoritative server returns the old value | The zone was not updated where delegation points | Confirm the domain’s active nameservers |
| Authoritative answer is new but local answer is old | A recursive cache has not expired | Compare TTL and another resolver |
| Website works but mail fails | MX or mail-related records differ | Compare the complete old and new zones |
| Only the www hostname fails | Its CNAME or A record was missed | Query the exact hostname, not only the root domain |
Plan A Lower-Risk DNS Cutover
- Inventory the existing A, AAAA, CNAME, MX, TXT, CAA, and service records.
- Lower the relevant TTL before the planned move, while the old answer is still correct.
- Build and test the destination website without changing public DNS.
- Make the smallest required record change and note the exact time.
- Keep the old service available during the cache window when possible.
- After the change, query the authoritative nameservers and at least two independent recursive resolvers.
Do not repeatedly change the record while caches are expiring. That creates multiple valid historical answers and makes diagnosis harder. Preserve a change log with the old value, new value, TTL, provider, and rollback condition.
Commands That Show The Source Of An Answer
Tools such as dig domain.example A, dig domain.example MX, and dig @authoritative-name-server domain.example A separate the record type and the server answering the question. A trace can show the delegation path. Browser cache clearing alone does not clear an internet provider’s recursive DNS cache.
For a standards-based explanation of TTL handling, see RFC 1035. When Cyclone Hosting manages the DNS zone, include the exact hostname and record type in a support ticket.