Understand propagation and diagnose DNS
Identify old values, external delegation or configuration conflicts.
Guide to the current versionGuide contents
Before you begin
- A signed-in customer account with a service assigned to it.
Why results can differ between devices#
DNS resolvers cache answers for their TTL. A change confirmed on authoritative servers does not immediately erase old answers at your Internet provider.
An answer saying a name does not exist may also be cached. Lowering TTL after a change does not erase time already cached.
Check in the right order#
- In domain details, verify that the DNS operation is complete.
- Check Nameservers: if the domain uses external servers, publish records at that provider or prepare a delegation change.
- In DNS zone, verify the exact name, type and target. www and the domain root are different names.
- For a website, also check IPv6: an outdated AAAA can send some visitors to another machine.
- After the previous cache duration, test again. For a persistent HTTPS error, check web server and certificate configuration.
Symptoms and checks#
| Symptom | Useful check |
|---|---|
| The zone has the right IP but the website is still old | DNS cache, AAAA record, proxy or cached 301 redirect. |
| The IP responds but the domain does not | Domain configuration on the web server, DNS and certificate. |
| The website works but email does not | MX and mailbox configuration; web DNS alone is insufficient. |
| The change is shown as pending | Wait for publication or registry confirmation and check History. |
Revert a change#
Restore only values you changed, then wait for propagation. A rollback is itself a DNS change.
Before changing nameservers, copy every required record, including email records. An empty zone at the new provider interrupts services.
Ready to get started?
Manage my domains ↗