Got a JAMB or WAEC student at home? Free CBT practice, daily questions, and monthly cash rewards for top students on the WNG Student Hub.Practice Free

How to Troubleshoot DNS Problems

How to Troubleshoot DNS Problems

Community › Domain Names

Frank ApokwuezeWinig
1156 discussions | 33 replies

7 views

How to Troubleshoot DNS Problems

DNS, or the Domain Name System, is responsible for translating a domain name such as example.com into the IP address that computers use to locate the website. When DNS stops working correctly, a website may fail to load even though the server itself is perfectly fine.

Common symptoms include “DNS_PROBE_FINISHED_NXDOMAIN,” “DNS server not responding,” “server IP address could not be found,” websites loading intermittently, email delivery problems, or a domain working on one network but not another.

A practical DNS troubleshooting process should move from the simplest possible causes to more advanced ones.

1. Confirm That the Problem Is Actually DNS

First, determine whether the problem affects the domain name or the server itself.

Try opening the website using its domain name. Then, if you know the server’s IP address, try accessing the IP address directly.

If the IP address works but the domain name does not, DNS is a strong suspect.

Also try the domain from another device or network. For example, test it using mobile data instead of your Wi-Fi connection.

If the website works on mobile data but not your Wi-Fi network, the problem could be your router, local DNS resolver, ISP DNS service, or cached DNS information.

2. Check Whether the Domain Name Is Correct

A surprisingly common DNS problem is simply entering the wrong domain.

Check:

  • Spelling of the domain
  • Correct top-level domain such as .com, .ng, .org, or .net
  • Whether www is being used correctly
  • Whether you are testing the intended subdomain

For example, www.example.com and example.com can have different DNS records.

3. Check the Domain’s DNS Records

The next step is to inspect the DNS records configured for the domain.

Important records include:

A record: Connects a domain or hostname to an IPv4 address.

AAAA record: Connects a hostname to an IPv6 address.

CNAME record: Points one hostname to another hostname.

MX record: Determines where email for the domain should be delivered.

NS record: Identifies the authoritative nameservers for the domain.

TXT record: Stores text-based information used for services such as email authentication and domain verification.

If an A record points to the wrong IP address, visitors may be sent to the wrong server.

If an MX record is incorrect, the website may work normally while email stops working.

4. Use DNS Lookup Tools

Command-line DNS tools can help you identify exactly where the problem occurs.

On Windows, you can use:

nslookup example.com

You can also query a particular DNS server:

nslookup example.com 8.8.8.8

On Linux and macOS, useful commands include:

dig example.com

and:

dig example.com A

You can also check nameservers:

dig example.com NS

These commands can reveal whether the DNS resolver can find the requested record.

5. Compare Different DNS Resolvers

If your normal DNS server is returning an error, test another resolver.

For example, you can compare responses from different public DNS services.

nslookup example.com 8.8.8.8

and:

nslookup example.com 1.1.1.1

If one resolver returns the correct address while another does not, the problem may involve DNS caching, propagation, or a resolver-specific issue.

6. Flush Your Local DNS Cache

Your computer may have stored an old DNS response.

On Windows, open Command Prompt and run:

ipconfig /flushdns

You should receive confirmation that the DNS resolver cache was successfully flushed.

Afterwards, try loading the website again.

On macOS and Linux, the appropriate DNS cache-clearing command depends on the operating system and DNS service being used.

7. Restart Your Router

Your router may be caching DNS information or experiencing a temporary DNS-related problem.

Restarting the router can force it to establish fresh connections and obtain new DNS information.

After restarting, test the website again.

If other devices connected to the same router have the same problem, the router or upstream DNS service becomes a more likely suspect.

8. Check Your Computer’s DNS Settings

Your device may be configured to use an incorrect or unavailable DNS server.

Check the network adapter’s DNS settings.

If the device is configured manually, verify that the addresses are correct.

You can temporarily test another DNS resolver to determine whether the problem is related to your configured DNS service.

However, changing DNS servers should be treated as a troubleshooting test rather than automatically assuming that your existing DNS provider is the problem.

9. Check the Nameservers at the Domain Registrar

One of the most important DNS troubleshooting steps is checking the nameservers assigned to the domain.

For example, if your domain’s DNS is managed by one provider but the domain is still using nameservers from an old hosting company, changes made in the new DNS management panel may have no effect.

You need to establish:

Who is the domain registrar?

Which nameservers does the domain currently use?

Where are the authoritative DNS records managed?

This distinction is extremely important.

Changing an A record in the wrong DNS control panel will not solve the problem because that DNS zone may not be authoritative.

10. Check DNS Propagation

DNS changes are not necessarily visible everywhere immediately.

If you recently changed nameservers, A records, CNAME records, MX records, or other DNS settings, different DNS resolvers may temporarily provide different answers.

This can make a website appear to work for one person but not another.

When troubleshooting propagation, compare the DNS response from several locations and resolvers.

Do not immediately assume that inconsistent results mean the DNS configuration is permanently broken.

11. Check for Missing or Incorrect A and AAAA Records

Suppose your website should point to:

example.com → 203.0.113.10

but the A record points somewhere else.

Visitors could be directed to the wrong server.

IPv6 can introduce another complication.

If an AAAA record exists but points to an incorrect IPv6 address, users whose networks prefer IPv6 may experience problems even though IPv4 users can access the website normally.

Therefore, check both:

A
AAAA

when troubleshooting website connectivity.

12. Check CNAME Records

CNAME problems are particularly common with subdomains and third-party services.

For example:

blog.example.com CNAME example.hostingprovider.com

If the CNAME target is incorrect, deleted, or no longer supported, the subdomain may stop working.

Also remember that DNS records have structural rules. A hostname configured as a CNAME generally cannot simultaneously have other record types at the same name in the traditional DNS model.

13. Investigate NXDOMAIN Errors

An NXDOMAIN response generally means that the queried domain name does not exist from the perspective of the DNS resolver.

For example:

DNS_PROBE_FINISHED_NXDOMAIN

could indicate:

  • The hostname does not exist
  • The DNS record was deleted
  • The domain’s nameservers are incorrect
  • The domain has expired
  • DNS delegation is broken
  • You are querying the wrong hostname
  • A DNS change has not propagated everywhere yet

Do not automatically conclude that the web server is offline. NXDOMAIN is fundamentally a DNS-level response.

14. Check Whether the Domain Has Expired

A domain that has expired can stop resolving correctly.

Check the domain’s registration status through the relevant registrar or registry information.

If the domain has expired, fixing the website’s A record will not necessarily solve the problem.

The domain registration and DNS configuration are related but separate components.

15. Check DNSSEC

DNSSEC provides cryptographic authentication for DNS information, but a misconfigured DNSSEC setup can cause domains to become unreachable.

If DNS records appear correct but some resolvers return validation-related errors, investigate DNSSEC.

Common causes include:

  • Incorrect DS records
  • Changed DNS providers without updating DNSSEC
  • Expired or incorrect signing keys
  • Broken DNSSEC configuration

DNSSEC problems can be particularly confusing because the domain may appear to work from some environments but fail from DNSSEC-validating resolvers.

16. Check Email DNS Separately

A website working does not mean the domain’s email configuration is correct.

For email problems, inspect the MX records:

dig example.com MX

Then check related authentication records such as:

SPF
DKIM
DMARC

An incorrect MX record can prevent incoming email.

Incorrect SPF, DKIM, or DMARC configuration can contribute to messages being rejected, quarantined, or classified as spam.

17. Check the TTL

TTL, or Time to Live, determines how long DNS information can be cached by resolvers.

For example:

TTL = 3600

means the record may be cached for approximately one hour, subject to DNS behaviour and resolver policies.

When troubleshooting recent DNS changes, remember that old information may remain cached until the relevant TTL expires.

18. Check Your Hosting Provider

If DNS resolves to the correct IP address but the website still does not load, the problem may no longer be DNS.

You may instead be dealing with:

  • Web server failure
  • Firewall restrictions
  • Incorrect virtual-host configuration
  • SSL/TLS problems
  • Hosting account suspension
  • Server overload
  • Application errors
  • CDN configuration problems

This is why troubleshooting should identify where the failure occurs instead of treating every website-access problem as a DNS problem.

19. Follow the DNS Resolution Chain

For more advanced troubleshooting, think about DNS as a chain:

Your device → DNS resolver → root servers → TLD nameservers → authoritative nameserver → DNS record

A failure anywhere along that chain can affect resolution.

Tools such as dig +trace can help investigate the path:

dig +trace example.com

This can reveal where resolution stops.

20. Use a Simple Troubleshooting Sequence

When a website suddenly stops resolving, work through the problem systematically:

Step 1: Check whether other websites work.

Step 2: Test the domain from another network.

Step 3: Run nslookup or dig.

Step 4: Check the A and AAAA records.

Step 5: Check the authoritative nameservers.

Step 6: Compare results using multiple DNS resolvers.

Step 7: Flush local DNS cache.

Step 8: Restart the router if appropriate.

Step 9: Check domain registration status.

Step 10: Check DNSSEC if enabled.

Step 11: If DNS resolves correctly, investigate the hosting server.

The key principle is simple: do not guess where the problem is. Trace the DNS resolution process until you find the point where the expected answer changes or disappears.

For beginners learning website management, DNS troubleshooting becomes much easier once you understand the difference between a domain registrar, DNS provider, nameserver, DNS record, hosting server, and DNS resolver. They are connected, but they perform different jobs.

Join the conversation. What is your own experience with this? Share your answer below, ask a follow-up question, or post what worked for you.
Frank Apokwueze
https://www.franklyntechnologies.com.ng

Frank Apokwueze is a technology enthusiast, website developer, SEO strategist, and digital business advocate passionate about helping individuals and businesses build a stronger presence online. Through Franklyn Technologies, he shares practical insights on website development, SEO, digital marketing, online business, and emerging technology to help readers understand and take advantage of the digital world.

Post a reply