Sign in Subscribe
Network+

Troubleshooting Common DNS Issues for Beginners

This post walks network beginners through the most common DNS issues they're likely to encounter, from stale cache entries to misconfigured DNS server settings. It provides a practical, step-by-step troubleshooting workflow using built-in tools like nslookup and ipconfig. Aligned with CompTIA Netwo

Jay Whale

• 3 min read
Troubleshooting Common DNS Issues for Beginners

If you've ever typed a website address into your browser and been met with a "Server Not Found" or "DNS_PROBE_FINISHED_NXDOMAIN" error, you've already encountered a DNS issue. For anyone starting out in networking, DNS problems are among the most common you'll see. The good news is that most of them follow predictable patterns and have straightforward fixes.

This post walks you through the most common DNS issues, how to identify them, and how to resolve them. By the end, you'll have a solid troubleshooting workflow you can rely on.

What Is DNS and Why Does It Break?

DNS (Domain Name System) translates human-readable domain names like www.google.com into IP addresses that computers use to communicate. Think of it as the phonebook of the internet. When DNS stops working, your device can't find the address it's looking for, even if your internet connection itself is perfectly fine.

DNS failures typically fall into a few categories: misconfigured settings, stale cached records, unreachable DNS servers, or issues on the authoritative side. Let's work through each one.

Step 1: Confirm DNS Is Actually the Problem

Before assuming DNS is at fault, verify that the issue isn't simply no internet connectivity. Try pinging a known IP address directly:

ping 8.8.8.8

If that succeeds but visiting a website by name fails, DNS is almost certainly the issue. If the ping fails too, you're dealing with a broader connectivity problem, not just DNS.

Step 2: Check Your DNS Server Settings

Your device needs to know which DNS server to query. On Windows, you can check your current DNS configuration with:

ipconfig /all

Look for the "DNS Servers" line in the output. If it shows 0.0.0.0 or is blank, your device hasn't received valid DNS settings, often a sign of a DHCP problem. Try setting a public DNS server manually:

  • Google DNS: 8.8.8.8 and 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 and 1.0.0.1

If switching to a public DNS resolves the issue, your original DNS server (likely your router or ISP's server) is the problem.

Step 3: Flush the DNS Cache

Your operating system caches DNS responses to speed things up. But stale or corrupted cache entries can cause resolution failures, especially after a website changes its IP address. Clearing the cache forces a fresh lookup.

On Windows:

ipconfig /flushdns

On Linux or macOS (varies by distro/version):

sudo systemd-resolve --flush-caches

After flushing, try accessing the site again. This resolves a surprising number of DNS issues that seem mysterious at first glance.

Step 4: Test DNS Resolution Directly

Use nslookup to manually query a DNS server and see what it returns:

nslookup www.google.com

You'll see the server being queried and the resolved IP address. You can also specify a different DNS server to test against:

nslookup www.google.com 8.8.8.8

If querying 8.8.8.8 works but your local DNS server doesn't return results, the issue is isolated to your DNS server, not the internet or the domain itself.

Common DNS Issues and Their Fixes

  • Wrong DNS server address: Verify settings via ipconfig /all and correct manually if needed.
  • Stale cache entries: Run ipconfig /flushdns to clear and refresh.
  • DNS server unreachable: Switch to a public DNS like 8.8.8.8 to confirm, then check your router or local server.
  • Typo in the domain name: Always double-check the URL. NXDOMAIN errors often come from simple typos.
  • Firewall blocking DNS traffic: DNS uses port 53 over both UDP and TCP. Make sure your firewall isn't blocking outbound traffic on this port.

A Quick Troubleshooting Checklist

  1. Ping a known IP (8.8.8.8) to rule out general connectivity issues.
  2. Check DNS server settings with ipconfig /all.
  3. Flush the DNS cache with ipconfig /flushdns.
  4. Use nslookup to test resolution against multiple servers.
  5. Try a public DNS server to isolate whether your local DNS is the culprit.

What's Next

Now that you understand DNS troubleshooting basics, the natural next step is diving into how DHCP works and what happens when devices can't get an IP address. DHCP and DNS issues often appear together in real-world scenarios, so understanding both gives you a much stronger foundation for network troubleshooting.

🔧
For ongoing DNS health visibility, PRTG Network Monitor lets you set up DNS sensors that alert you the moment resolution fails — great for catching issues before users do rather than troubleshooting reactively. PRTG Network Monitor, dnstracer and Dog (DNS client).

Tools and resources for this topic