Ping -a not Resolving

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sean - 15 Sep 2004 16:34 GMT

I have just inherited an old NT 4.0 network. They have a
DNS server here but with very few hosts added. They claim
in February when they installed this one off Linux
firewall that Ping -a stopped resolving names.
Since this is NT 4 should not WINS finally produce the
NetBIOS name of the IP address? Also I added an A record
for a host in the DNS server my station points too but
ping -a only produces an IP address.

Thanks
Sean

Reply to this Message

Jeff Cochran - 16 Sep 2004 14:12 GMT

>I have just inherited an old NT 4.0 network. They have a
>DNS server here but with very few hosts added. They claim
[quoted text clipped - 4 lines]
>for a host in the DNS server my station points too but
>ping -a only produces an IP address.

NetBIOS name resolution may or may not work in place of TCP/IP
resolution, depending on how the client and DNS are configured.
Especially if you don't use WINS. Try a nslookup or dig and see waht
really is resolving.

Jeff

Reply to this Message

Sean - 16 Sep 2004 15:43 GMT

>-----Original Message-----
>
[quoted text clipped - 15 lines]
>.
>Below is the default response from Nslookup. Looks to me

that DNS is not functioning correctly on the NT 4 server.
I have a host record for 172.16.10.1 and it is the PDC. I
also have WINS running, resources are available on the
network. Kind of confused at the moment.
U:\>nslookup
*** Can't find server name for address 172.16.10.1: Non-
existent domain
Default Server: 172.16.0.1
Address: 172.16.0.1

The default server here is the firewall which is acting as
a DNS proxy and forwarding to a public name server.

Thanks Again to all or anyone who responds.
Sean

Reply to this Message

Jeff Cochran - 18 Sep 2004 15:54 GMT

>>-----Original Message-----
>>On Wed, 15 Sep 2004 08:34:55 -0700, "Sean"
[quoted text clipped - 36 lines]
>The default server here is the firewall which is acting as
>a DNS proxy and forwarding to a public name server.

Then it likely won't use WINS for DNS lookups, and since you ping a
system that is in the domain served by the DNS that can't be resolved
by it, the name doesn't exist. Ping doesn't look at your DNS and then
assume it might be somewhere else if DNS doesn't resolve it. And if
DNS is authoritative for the domain and doesn't have the host name,
then for name resolution that host doesn't exist.

Jeff

Reply to this Message