DNS Troubleshooting by Symptom: Fix Missing Websites, Email Errors, and SSL Verification Failures
DNSwebsite errorsemail setupSSLdomain troubleshooting

DNS Troubleshooting by Symptom: Fix Missing Websites, Email Errors, and SSL Verification Failures

CClaimed.site Editorial Team
2026-11-14
7 min read

A symptom-based DNS troubleshooting checklist for website outages, email errors, SSL validation failures, and DNSSEC problems.

DNS problems often look alike: a website disappears, email stops arriving, or an SSL certificate cannot be verified. This symptom-based checklist helps you identify the responsible record, confirm which DNS provider is authoritative, compare expected and observed results, and make a safe correction without guessing.

Overview

The Domain Name System (DNS) connects human-readable names such as example.com to services such as a web server, mail provider, or certificate-validation endpoint. A domain can be registered with one company, use nameservers operated by another, and host its website somewhere else. That separation is the source of many troubleshooting errors: a record may be edited successfully in a control panel that is not actually answering queries for the domain.

Start by separating the problem into three questions:

  1. Who is authoritative? Identify the nameservers currently delegated at the registrar or registry level.
  2. What should the record return? Use the values supplied by your hosting, email, or certificate provider.
  3. What is the public DNS currently returning? Query the authoritative nameserver directly, then compare results from a public resolver.

Before changing anything, record the current DNS zone or export it if your provider supports that option. Note the time, the change made, the previous value, and the expected value. This creates a rollback point and prevents several people from making conflicting edits. For background on record types, see DNS Records Explained: A Practical Guide to A, CNAME, MX, TXT, and SRV Records.

Checklist by scenario

Website is not loading after a DNS change

  • Confirm the domain is not expired, suspended, or placed on a registrar hold.
  • Check the nameservers shown at the registrar. They must match the DNS provider where you edited the records.
  • Query the apex domain and the www host separately. An A record for example.com does not automatically configure www.example.com.
  • Confirm that the A record points to the correct IPv4 address, or that the AAAA record points to a working IPv6 address.
  • If the provider gave you a CNAME, use it on the hostname it specified. Do not place a CNAME beside another record with the same name.
  • Check the hosting account for a domain or virtual-host entry. Correct DNS alone will not make a server respond for a domain it has not been configured to recognize.
  • Test both the bare domain and www over HTTP and HTTPS. A redirect, application error, or certificate warning indicates a different layer of the setup.

Useful checks include dig example.com A, dig www.example.com CNAME, or nslookup example.com. To bypass a local resolver, query a known authoritative nameserver with dig @ns1.example-dns.com example.com A, replacing the nameserver with the one listed for your domain.

Email is not arriving or outgoing mail is being rejected

  • Verify that the MX records point to the mail provider’s exact hostnames and that each target has a valid address record.
  • Check the MX priority values. A lower numerical value generally indicates the preferred destination, but follow the mail provider’s instructions rather than inferring a design.
  • Remove old MX records only when you are certain the previous service is no longer needed. Two providers left in the same zone can send mail to different systems.
  • Confirm the domain’s SPF policy is published as one TXT record at the root. Avoid creating multiple independent SPF records.
  • Publish the DKIM TXT record at the selector hostname supplied by the email provider. Selectors are case-sensitive in some tools and differ between providers.
  • Add the required DMARC TXT record only after checking the reporting address and policy syntax. Begin with a policy appropriate to your testing stage.
  • Send a test from an address on the domain and inspect the message headers for SPF, DKIM, and DMARC results.

Use dig example.com MX and dig example.com TXT to inspect public records. If the records look correct but mail still fails, review mailbox status, provider logs, sender reputation controls, forwarding behavior, and the exact rejection message. DNS is only one part of email delivery.

SSL certificate verification fails

  • Read the certificate provider’s challenge instructions carefully. The required record may be a DNS CNAME or TXT record and usually has a precise host and value.
  • Enter only the host portion requested by the control panel. Some interfaces append the domain automatically, so entering the full name can create an unintended duplicate.
  • Check for conflicting records at the same hostname. A validation CNAME cannot normally coexist with a TXT or other incompatible record at that name.
  • Confirm the record is published at the authoritative DNS provider, not merely visible in a hosting dashboard.
  • Wait for the provider’s validation check to observe the record, then retry validation. Do not repeatedly replace a correct value unless the provider issued a new challenge.

DNSSEC produces errors or the domain intermittently fails

DNSSEC adds signatures that allow resolvers to validate DNS responses. An outdated DS record at the registrar, a changed DNS provider, or a missing signing key can produce validation failures even when ordinary DNS records appear correct. Check whether DNSSEC is enabled at both the registrar and DNS provider, and compare the registrar’s DS information with the currently published signing data. If you cannot reconcile them, use the provider’s documented recovery process before making changes. Avoid disabling DNSSEC casually, especially for a business-critical domain; record the existing settings and understand the effect of each step.

What to double-check

Authoritative nameservers

A nameserver change moves control of the DNS zone. If the registrar delegates the domain to Provider A while you edit records at Provider B, Provider B’s changes will not be visible publicly. Query the NS records with dig example.com NS, then inspect the zone at each listed nameserver.

Conflicting and duplicated records

Look for an A and CNAME record at the same hostname, multiple MX sets from old providers, duplicate SPF policies, and an AAAA record pointing to an unconfigured server. Also check for records created automatically by a website builder, CDN, email platform, or security service. A newly added record may not be the only record affecting the result.

TTL and caching

TTL controls how long a resolver may cache an answer; it is not a countdown that guarantees a change will be visible everywhere at one exact time. Lowering TTL after a change does not reliably remove answers already cached under a previous TTL. Compare the authoritative response with responses from more than one resolver, and use a private browser window only as a supplementary check—not as proof that DNS has updated.

Record formatting

Copy values exactly, including quotation marks where a provider requires them, trailing dots in fully qualified hostnames, and long TXT strings. Control panels differ: one may ask for @ for the root domain, while another leaves the host field blank. Follow the labels in the active DNS provider’s interface rather than assuming that two panels use the same notation.

Common mistakes

  • Changing nameservers and records at the same time: This makes it difficult to tell which change caused the outage. Move one control point at a time where possible.
  • Deleting the whole zone: A web record may be fixed while MX, SPF, DKIM, verification, or subdomain records are silently removed. Edit the affected record instead.
  • Assuming propagation is the only explanation: A wrong nameserver, typo, conflicting record, or server configuration issue will not resolve by waiting.
  • Using a proxy or CDN without checking its mode: A proxied hostname may return the proxy’s address rather than the origin address. Confirm whether the service expects proxying enabled or disabled.
  • Testing only one hostname: The apex domain, www, mail hostnames, and subdomains can use different records and services.
  • Making emergency edits without a backup: Save a zone export or screenshot, and keep a dated change log.

If a change has caused an outage, compare the current zone with the last known working version and revert only the affected entries. For broader domain administration, the Domain Security Checklist covers registrar access, locks, and other controls that sit outside the DNS zone.

When to revisit

Use this checklist whenever you move a website, change hosting, configure a new email provider, renew or replace an SSL certificate, launch a subdomain, enable a CDN, transfer a domain, or change DNSSEC settings. Revisit it before a seasonal campaign or other high-traffic launch, when a registrar or hosting provider changes its control panel, and after any security incident.

For a practical final pass, work in this order:

  1. Write down the intended service and exact record values.
  2. Confirm the registrar’s nameservers and identify the authoritative DNS provider.
  3. Export or document the current zone.
  4. Change only the required record, using the provider’s stated host and value format.
  5. Query the authoritative nameserver directly, then check independent public resolvers.
  6. Test the affected website, mail flow, or certificate challenge from the relevant service.
  7. Record the final values, time of change, and any follow-up needed.

If the domain is being moved between registrars or hosts, pair this process with the domain transfer checklist and confirm that backups and rollback plans are current before making the change.

Related Topics

#DNS#website errors#email setup#SSL#domain troubleshooting
C

Claimed.site Editorial Team

Technical SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.