DNS problems are often misdiagnosed as hosting, application, or email failures. This guide gives you a repeatable way to identify the record involved, compare recursive and authoritative answers, account for TTL and caching, and verify that a change is working for websites, subdomains, mail, certificates, and third-party services.
Overview
The Domain Name System translates names such as www.example.com into information that clients can use. An A record maps a name to an IPv4 address, an AAAA record maps it to an IPv6 address, a CNAME points one name to another name, MX records identify mail servers, and TXT records hold text used for verification and email-related configuration.
A useful DNS troubleshooting process separates three questions:
- What should the record say? Confirm the value supplied by your hosting provider, email service, certificate platform, or verification service.
- What does the authoritative DNS service publish? This is the source of truth for the zone, assuming the zone is configured correctly.
- What are recursive resolvers returning? Public and local resolvers may temporarily return cached answers from before the change.
Do not treat a DNS propagation checker as proof that a record is correct by itself. A checker can show that different resolvers have different cached answers, but you still need to validate the record type, name, value, and authoritative response.
What to track
Record types and common uses
| Record | Typical purpose | What to verify |
|---|---|---|
| A | Connects a hostname to an IPv4 address. | Correct address, hostname, and absence of an obsolete duplicate. |
| AAAA | Connects a hostname to an IPv6 address. | That the address is reachable and the service is configured for IPv6. |
| CNAME | Aliases one hostname to another hostname. | Exact target, trailing-dot normalization, and conflicts with other records. |
| MX | Routes email for a domain. | Priority values, mail hostnames, and A or AAAA records for those hosts. |
| TXT | Publishes verification or policy text. | Exact token, quoting, splitting of long values, and record name. |
| NS | Identifies authoritative name servers. | That the domain delegates to the DNS provider you are editing. |
| CAA | Restricts which certificate authorities may issue certificates. | Whether the requested issuer is permitted, where applicable. |
Start with the fully qualified name. The root domain, often written as example.com or @ in a provider dashboard, is different from www.example.com, mail.example.com, and _acme-challenge.example.com. A frequent error is entering a full name into a control panel that automatically appends the domain, creating a duplicated name.
Also check provider restrictions. Many DNS systems do not allow a CNAME at the zone apex, and a hostname generally should not have a CNAME alongside ordinary A, AAAA, MX, or TXT data. Dashboard interfaces may hide these rules or represent them differently, so inspect the resulting DNS response rather than relying only on the saved form.
Cadence and checkpoints
Use the following workflow whenever you launch a subdomain, migrate hosting, configure email, renew a certificate, or add a verification token.
1. Record the intended change
Keep the hostname, record type, expected value, TTL, time of change, and service owner in a small change log. Preserve the previous value until the new configuration has been tested. This makes rollback and later investigation much easier.
2. Confirm delegation
Query the domain's NS records first. If the domain is delegated to a different provider than the dashboard you edited, your change will not affect the live zone. Registrar settings, DNS hosting settings, and web hosting settings are often separate systems.
3. Query a recursive resolver
On a Unix-like system, use dig:
dig example.com A
dig www.example.com CNAME
dig example.com MX
dig example.com TXT
dig +short www.example.com A
For a more explicit response, remove the accidental leading space before the last command if copying it into a shell. On Windows, nslookup provides a comparable basic check:
nslookup -type=A www.example.com
nslookup -type=MX example.com
nslookup -type=TXT example.com
4. Query the authoritative server directly
First identify an authoritative name server, then ask it for the record:
dig example.com NS
dig @ns1.example-dns.net www.example.com A
dig @ns1.example-dns.net example.com TXT
Replace the name server with one returned by the NS query. If the authoritative answer is correct but a recursive resolver is old, the issue is likely caching or TTL timing. If the authoritative answer is wrong, propagation is not the problem; fix the zone configuration or delegation.
5. Compare from more than one network
Check a local resolver and at least one independent resolver. A corporate network, VPN, home router, browser, or operating system may cache DNS separately. Compare the answer, status, returned TTL, and whether the response contains an error such as NXDOMAIN or SERVFAIL.
How to interpret changes
TTL, or time to live, tells a recursive resolver how long it may cache an answer. It is not a guaranteed worldwide completion time. Some resolvers may retain an earlier answer until its cached lifetime ends, while other clients may encounter a newer answer sooner. Lowering a TTL immediately before a change may not help if the previous, higher TTL was already cached.
Different results usually point to different causes:
- Authoritative and recursive answers both show the new value: DNS is probably updated. Test the service itself, including HTTPS, application routing, or mail delivery.
- Authoritative answer is old: Check the edited zone, active name servers, record name, and whether another provider controls the domain.
- Authoritative answer is new but recursive answers vary: Allow for cached responses and compare the returned TTL values.
- NXDOMAIN: The queried name does not exist from that resolver's perspective. Check spelling, zone boundaries, delegation, and whether the record was created at the intended level.
- SERVFAIL: The resolver could not complete validation or resolution. Investigate broken delegation, unreachable name servers, DNSSEC issues, or invalid dependent records.
- Website works on IPv4 but not IPv6: Inspect the AAAA record and IPv6 server configuration. Removing or correcting an unusable AAAA record may be necessary while IPv6 support is fixed.
For email, verify MX records and then check that each referenced mail hostname resolves. A TXT record can be valid but still fail verification if it is attached to the wrong name, contains an extra character, or is split incorrectly by the provider. For certificates, confirm both the certificate challenge record and any CAA restriction that could affect issuance.
When to revisit
Review DNS after every infrastructure change and on a monthly or quarterly schedule for important domains. A lightweight recurring check should cover the root domain, key web subdomains, mail records, verification records, NS delegation, and any CAA or DNSSEC configuration that your team manages.
Revisit this checklist immediately when:
- a hosting, CDN, registrar, or DNS provider changes;
- a website migration or custom-domain connection is planned;
- mail delivery, certificate issuance, or service verification fails;
- one network sees a different result from another;
- an old IP address, provider hostname, or verification token may still be published; or
- DNSSEC, nameserver delegation, or domain ownership settings are modified.
For each review, save the command output or record a small snapshot of expected values, authoritative answers, and representative recursive answers. Test the application after DNS appears correct: load HTTP and HTTPS endpoints, verify redirects and certificates, send a controlled email test, or rerun the third-party verification. DNS troubleshooting is complete when both the DNS response and the dependent service behave as expected—not merely when a dashboard reports that a record was saved.