Windows 7 / Networking

Verifying that a Specific DNS Server Resolves Correctly

One of the most common sources of DNS resolution problems is the caching of an outdated DNS address. Particularly on the Internet, DNS servers might continue to return an outdated IP address several hours after a change has been made to the DNS server containing the record. If some clients are unable to correctly resolve an IP address but other systems resolve it correctly, one or more DNS servers have probably cached the incorrect address. To identify the problematic DNS servers, use Nslookup to manually query each server.

To verify that a specific DNS server is able to resolve a host name to the correct IP address, open a command prompt and run the following command.

nslookup hostname server_name_or_address

Nslookup will query the specified server only, regardless of the DNS servers configured on the client. If a specific server returns an incorrect IP address, that server is the source of the problem. Generally, this problem will resolve itself after the incorrect entry expires in the DNS server's cache. However, you can also resolve the problem by manually clearing the DNS server's cache.

[Previous] [Contents] [Next]

In this tutorial:

  1. Troubleshooting Network Issues
  2. Tools for Troubleshooting
  3. Table-1 Network Troubleshooting Tools
  4. Arp
  5. How to Identify a Problem with the ARP Cacher
  6. How to Clear the ARP Cache
  7. Event Viewer
  8. IPConfig
  9. Nblookup
  10. Nbtstat
  11. Net
  12. How to View Shared Folders on the Local Computer
  13. How to View Shared Folders on Another Computer
  14. Netstat
  15. Network Monitor
  16. Nslookup
  17. Verifying that the Default DNS Server Resolves Correctly
  18. Verifying that a Specific DNS Server Resolves Correctly
  19. Verifying Specific Types of Addresses
  20. Using TCP for DNS Lookups
  21. PathPing
  22. PathPing Output
  23. Routing Loops
  24. Performance Problems
  25. Possible Connectivity Issues
  26. No Connectivity Issues
  27. Performance Monitor
  28. Data Collector Sets
  29. Windows Resource Monitor
  30. Ping
  31. PortQry
  32. Identifying the TCP Port for a Service
  33. Windows 7 Testing Service Connectivity
  34. Determining Available Remote Management Protocols
  35. Why PortQry Is Great
  36. Route
  37. Task Manager
  38. TCPView
  39. Telnet Client
  40. Testing Service Connectivity
  41. Test TCP
  42. Windows Network Diagnostics
  43. The Process of Troubleshooting Network Problems
  44. How to Troubleshoot Network Connectivity Problems
  45. How to Troubleshoot Application Connectivity Problems
  46. Default Port Assignments for Common Services and Tasks
  47. How to Troubleshoot Name Resolution Problems
  48. How to Verify Connectivity to a DNS Server
  49. How to Use the Hosts File
  50. How to Troubleshoot Performance Problems and Intermittent Connectivity Issues
  51. How to Troubleshoot Joining or Logging on to a Domain
  52. How to Verify Requirements for Joining a Domain
  53. How to Troubleshoot Network Discovery
  54. How to Troubleshoot File and Printer Sharing
  55. How to Troubleshoot File and Printer Sharing from the Client
  56. How to Troubleshoot File and Printer Sharing from the Server
  57. How to Troubleshoot Wireless Networks
  58. Network Diagnostics
  59. How to Troubleshoot Firewall Problems