How to Troubleshoot Common DNS Problems Print

  • DNS troubleshooting
  • 1883

DNS configuration affects how visitors reach your website, how email is delivered, and how connected services verify your domain.

A small DNS error can cause a website to load incorrectly, email to stop arriving, or a service verification request to fail.

This guide explains common DNS problems, what to check, and how to approach troubleshooting without making unnecessary changes.

1. Your Domain Does Not Open Your Website

If your domain does not display the expected website, start by checking the DNS destination.

Review:

  • The domain's authoritative nameservers.

  • The A record for the root domain.

  • The AAAA record, if one is configured.

  • The CNAME record for www, if applicable.

  • Whether the hosting service is active.

  • Whether the domain has been added to the correct hosting configuration.

Compare the DNS values with the exact information supplied by your hosting provider.

If you recently changed DNS settings, the previous information may still be cached by some resolvers. See the guide on DNS propagation for more information.

2. Your Website Works Without WWW but Not With WWW

The root domain and the www hostname may use separate DNS records.

For example:

  • example.com

  • www.example.com

If one works and the other does not, review the DNS record for the hostname that is failing.

Confirm that the www record points to the intended destination and that your hosting configuration recognizes both hostnames.

3. Your Website Displays an Old Version

If DNS was recently changed, some visitors may still reach an older destination because of cached DNS information.

However, an outdated website can also result from:

  • Browser caching.

  • Website or application caching.

  • A content delivery network (CDN) cache.

  • Changes not yet published to the active website directory.

  • The domain pointing to a different hosting destination than expected.

Check the DNS destination first, then investigate the relevant website or network cache.

4. Your Email Is Not Being Delivered

Email delivery depends on several DNS records and the configuration of your email service.

Review the records supplied by your email provider, especially:

  • MX records, which identify incoming mail servers.

  • TXT records used for SPF and other email authentication settings.

  • DKIM records, if required by your provider.

  • DMARC records, if configured for your domain.

Do not delete or replace email-related records simply to make a website work. Website and email DNS settings serve different purposes and must be maintained together.

If you recently changed nameservers, confirm that the required email records were recreated in the active DNS zone.

5. A Domain Verification Request Fails

A website platform, email service, or other provider may ask you to add a TXT or CNAME record to verify your domain.

If verification fails:

  1. Confirm that you are editing the active DNS zone.

  2. Check the hostname or record name requested by the provider.

  3. Copy the entire record value exactly.

  4. Confirm that the record type is correct.

  5. Check for accidental spaces, missing characters, or duplicate records.

  6. Allow time for the DNS change to become visible.

  7. Retry verification using the provider's instructions.

Some providers expect a value entered as a full hostname, while others expect only the hostname label. Follow the format specified by the provider.

6. You Changed Nameservers and Services Stopped Working

Changing nameservers changes which DNS provider is authoritative for your domain.

The new DNS zone must contain the records needed by all connected services, including:

  • Website hosting.

  • Professional email.

  • Domain verification.

  • Subdomains.

  • Third-party applications.

Before changing nameservers, document the existing records and recreate the required entries with the new DNS provider.

7. Your DNS Changes Are Not Visible Yet

DNS resolvers may cache previous answers. Check the record using more than one DNS lookup service and confirm the authoritative nameservers.

Avoid repeatedly changing the same record while waiting. Additional changes can make it harder to identify the original problem.

A Safe DNS Troubleshooting Checklist

Before changing any settings:

  1. Write down the exact domain and hostname affected.

  2. Identify the service that is not working.

  3. Confirm which provider manages the authoritative DNS zone.

  4. Save or document the current DNS records.

  5. Compare the existing values with the service provider's instructions.

  6. Change only the record that needs correction.

  7. Allow time for DNS caching and updates.

  8. Test the website, email, or service again.

Need Help Diagnosing a DNS Problem?

Contact WebDaddy Pro Support if you cannot identify the cause.

Include:

  • Your domain name.

  • The affected hostname, if applicable.

  • The service that is not working.

  • Any recent DNS or nameserver changes.

  • The error message or behavior you are seeing.

Never include passwords, API keys, email credentials, or other private account information in a support request.


Was this answer helpful?

« Back