I CAN PING THROUGH IP&LOCALHOST NAME BUT I CAN NOT PING THROUGH FQDN

Tags:

Last response: January 31, 2013 11:06 AM in Networking

nilesh05

January 31, 2013 5:56:51 AM

Dear Sir,
I can not get ping test with a FQDN.
Following are the steps I follow.

1. When I ping by IP its fine.
C:\Documents and Settings\Administrator.XXXXXXXX>ping 192.168.100.66

Pinging 192.168.100.66 with 32 bytes of data:

Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128

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

2. When I ping by localhost name it’s also work.

C:\Documents and Settings\Administrator.XXXXXXXX>ping live
Pinging live [192.168.100.66] with 32 bytes of data:
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128
Reply from 192.168.100.66: bytes=32 time<1ms TTL=128

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

3. But when I ping by FQDN following error are occurring.

C:\Documents and Settings\Administrator.XXXXXXXX>ping live.XXXXXXXX.com

Ping request could not find host live.bedmuthawire.com. Please check the name and
try again.

More about : ping localhost ping fqdn

| E-mail me updates
| Report abuse

Reply to nilesh05

bill001g

January 31, 2013 11:06:08 AM

Short answer is you must fix the DNS.

I suspect if you are running like most users who post on this forum you do not have your own DNS server. There are a number of issues but the most common is that the IP address resolves to a real IP but you are behind your router which means you need to use the local lan ip. If this is your problem the easy fix is to put a entry into the host file to override the DNS. This also works when you can't figure out the DNS problem and just want to give up.

You could try the NSLOOPUP command so you can actually see what the DNS server is sending and what DNS server you are using.

If you have your own internal DNS server then it likely just a simple misconfiguration.