can't find server name for 192.168.100.xxx/unknown server

a new dns server on a windows 2003 standard server ( stand alone, not a DC or
in a domain ) seems to resolve forward and reverse lookups okay on that
machine. but when doing lookups from either that machine or a remote machine
it returns the message 'cant find server name for 192.168.100.xxx' then
'server: unknown/ address: 192.168.100.xxx' for the resolving server info.
where does this info have the be configured ? does the server have to be a
DC to effectively display the server name info ? and also, where does one
enter the notify info for the secondary dns zone transfers ? tia ...

 

You seem to be referring to the informational message given when
using nslookup if the DNS server that is being used does not have
a PTR record allowing nslookup to get the servers name from a
reverse lookup of the IP that is being used for resolution.

If you want the nslookup informational message to go away then
you need to define a reverse zone and list the server in it (since
this is a private IP subnet involved here, else you would need to
get the server listed with a PTR in the correct reverse zone,
defining one if needed/appropriate).

 

Does a PTR exist for the address of the DNS server?

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

hi, thanks for the reply guys. it actually is using a public ip address but
i changed the #s for the post. it does have a ptr record for the server, but
this is the other odd thing that is throwing me: when on the server itself
it will resolve reverse lookups for that server and zone correctly when given
an ip address, but other machines that use different dns servers will not
resolve the reverse lookups ( although the successfully resolve the forward
lookups for the domain name ). i double-checked the dns info with the
registrar and everything seems to be correct, so i am not sure what i am
missing here (?) ...

 

If it you use a public IP address, then the owner of the Reverse lookup for
the public address has to create the PTR. It is usually your ISP that is
responsible for the PTR for your public address, unless they delegate it to
another DNS. I have seen cases, especially with small ISPs, that the reverse
look is still owned by the provider they get their addresses from.



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

 

hi, thanks again for the reply. after much effort into investigating this it
did in fact turn out to be an issue with the isp just as you had said.