Skip to content

Guide

DNS Troubleshooting for Help Desk Tickets

Illustration of a globe with a magnifying glass representing DNS troubleshooting

Short answer

When a user can reach a site by IP address but not by name, the problem is almost always DNS. Check the configured DNS servers with ipconfig /all, test name resolution with nslookup, clear the local cache with ipconfig /flushdns, and establish whether the failure affects one machine or everybody on the network.

DNS is like a phone book for the internet. When you type a website name like example.com, your computer asks a DNS server to look up the real number address behind that name, called an IP address. When DNS breaks, websites will not load, even though the internet connection itself is working just fine.

How to check if DNS is the problem

  1. Try opening a website by typing its normal name, like example.com.
  2. If that fails, try opening a website using its number address instead of its name. You can find a number address by asking a search engine for the IP address of a well known site.
  3. If the number address works but the name does not, the problem is DNS, not the internet connection itself.
  4. Ask if this is happening on more than one device on the same network. If it is, the problem may be with a shared network setting, not just one computer.

How to fix a DNS problem on a Windows computer

  1. Open the command prompt. You can search for it in the Windows start menu.
  2. Type ipconfig slash flushdns and press enter. This clears out old, saved address information that may be wrong.
  3. Type ipconfig slash release, press enter, then type ipconfig slash renew and press enter. This asks the network for a fresh set of address information.
  4. Restart the computer, since this clears out many small networking problems.
  5. Check the DNS server address in the network settings. If it looks wrong or was typed in by hand, try switching it back to automatic.

Always write down which DNS server the computer was using and what happened when you tested it. That small detail often turns a five minute ticket into a quick, confident fix instead of a repeated guessing game.

Common questions

How do you know a problem is DNS?
If the address works but the name does not, it is DNS. Pinging a known IP address successfully while the same site fails by name isolates the fault to name resolution rather than connectivity.
What commands do you use to troubleshoot DNS?
Use ipconfig /all to see which DNS servers the machine is using, nslookup to test whether a name resolves and which server answered, and ipconfig /flushdns to clear a stale cached record. Those three cover most Tier 1 DNS tickets.
What causes DNS problems on a single computer?
Usually a manually configured DNS server that is no longer valid, a stale cache entry, or a VPN client that changed the resolver and did not clean up after itself. If only one machine is affected, look at its own configuration before blaming the network.

Related guides