How to ”Quickly” Test DNS Resolution

  1. You have to see if DNS resolution is working you can see if the DNS server you are configured to query knows what it?s talking about. Using the NSLOOKUP command shows this information.
C:\WINDOWS\SYSTEM32>nslookup
Default Server:? ns3.srv.hcvlny.cv.net
Address:? 167.206.112.3

> www.yahoo.com
Server:? ns3.srv.hcvlny.cv.net
Address:? 167.206.112.3

Non-authoritative answer:
Name:? ? ? www.yahoo.akadns.net
Addresses:? 216.109.118.74, 216.109.118.75, 216.109.118.77, 216.109.117.110
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 216.109.117.204, 216.109.117.205, 216.109.118.69, 216.109.118.71
Aliases:? www.yahoo.com

  1. When I query my local DNS server, I can see that Yahoo.com has multiple IP addresses that can be used.
  2. Now, it?s possible to ping with the ?a switch to also verify if DNS resolution is work. Pinging Yahoo?s IP address with the ?a switch produces the DNS name of the system.
C:\WINDOWS\SYSTEM32>ping -a 216.109.118.74

Pinging p11.www.dcn.yahoo.com [216.109.118.74] with 32 bytes of data:

Reply from 216.109.118.74: bytes=32 time=22ms TTL=51
Reply from 216.109.118.74: bytes=32 time=25ms TTL=51
Reply from 216.109.118.74: bytes=32 time=27ms TTL=51
Reply from 216.109.118.74: bytes=32 time=32ms TTL=51

Ping statistics for 216.109.118.74:
? ? ? Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
? ? ? Minimum = 22ms, Maximum = 32ms, Average = 26ms

Leave a Reply

You must be logged in to post a comment.