DNS troubleshooting
Symptoms
- The website does not open, or opens the wrong site.
- Email is not sent or not received after a DNS change.
- A new domain does not resolve.
- Some visitors see the site and others do not.
Common causes
- The record was edited at the wrong DNS provider.
- A change has not finished spreading, because of the TTL.
- A record is missing, duplicated or spelled incorrectly.
- Two SPF records exist on the same domain.
- The nameservers changed without the same records being created first.
Safe initial checks
Find the DNS provider. Read Find your DNS provider.
Look up the records from a terminal. These commands only read data:
bashdig NS yourdomain.com +short dig A yourdomain.com +short dig MX yourdomain.com +short dig TXT yourdomain.com +shortCompare the answers with the values in the DNS provider you identified.
Wait if you changed a record recently. The TTL controls how long old answers remain in use.
Do not change nameservers to fix a single record
Changing nameservers moves the whole zone. Edit the one record that is wrong instead, in the provider that manages it.
Step-by-step solutions
- Wrong provider. If the answers do not match your records, edit the records at the provider the lookup names, not at a different one.
- Missing record. Add the record with the correct host, type and value. Read DNS record types to choose the right type.
- Duplicate SPF records. Combine them into one
v=spf1record. See TXT records. - Old answers still returned. Wait for the TTL to pass, then check again.
- Nameservers changed but records are missing. Restore the previous nameservers, create every record at the new provider, then change the nameservers again. See Change nameservers.
How to confirm the issue is fixed
- The
diganswers match the records you intended. - The website opens over HTTPS in a browser.
- A test email is delivered, and a test message from the mail service is received.
When to contact support
Contact support if you cannot find the DNS provider, if the DNS editor is missing from your panel, or if a change you made has stopped the website or email and you cannot restore the previous state.
Information to include in a support ticket
- The domain name and the service involved.
- The output of the
digcommands above. - The time you made the last change and what you changed.
- The exact error message, if any.
Related articles
- Find your DNS provider
- DNS record types
- Domain connected but not visible
- Email and website stopped after DNS changes
Last reviewed
2026-10-27
