Problems resolving DNS with an Windows NT DNS forwarder

[fmcastillo]

HI,

I got some issues with an Windows NT DNS server used as a
forwarder for a WIndows 2k DNS server. The DNS clients
seems to have problems resolving addresses that are being
contacted through the forwarder. For example, if I try to
ping to a address using just

ping servername

I recieve no response, but if I use the complete hostname
(with the domain included)

ping servername.domain.com

I recieve response here. Also when I try to ping to an
hostname defined on the Win2k DNS server, I'm not
recieving the ping response with the complete hostname (I
mean, with the domain name included). I'm recieving
something like this

ping servername

pinging servername {xxx.xxx.xxx.xxx} with 32 bytes of data
reply ....
reply ...
reply ...
reply ...

I think I should be recieving something like

pinging servername.domain.com {xxx.xxx.xxx.xxx} with 32
bytes of data
reply ...
reply ...
reply ...
reply ...

Any suggestions ???

Thanks,

FC

 

[Michael Johnston [MSFT]]

This would indicate that the DNS suffix on the client or the DNS suffix search order does not include the zone conigured on the DNS server. Also, when ping
simply returns the hostname of the machine you are pining, this indicates that WINS or netbios broadcast resolved the name not DNS. Make sure that the
client's primary DNS suffix or DNS suffix search order includes the suffix for the zone that the resource exists in.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Guest]

Problem fixed !!! .. thanks !!!

-----Original Message-----
This would indicate that the DNS suffix on the client or

the DNS suffix search order does not include the zone
conigured on the DNS server. Also, when ping

simply returns the hostname of the machine you are

pining, this indicates that WINS or netbios broadcast
resolved the name not DNS. Make sure that the

client's primary DNS suffix or DNS suffix search order

includes the suffix for the zone that the resource exists
in.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from which they originated.

 

[FC]

Do you know if this is related with the Reverse lookup ? I
tryied to use it but doesn't seem to be working at all,
even though the servers and computers registered appears
on the reverse lookup zone over the DNS administrator

-----Original Message-----
This would indicate that the DNS suffix on the client or

the DNS suffix search order does not include the zone
conigured on the DNS server. Also, when ping

simply returns the hostname of the machine you are

pining, this indicates that WINS or netbios broadcast
resolved the name not DNS. Make sure that the

client's primary DNS suffix or DNS suffix search order

includes the suffix for the zone that the resource exists
in.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from which they originated.