reverse DNS lookup problem

reverse DNS lookup problem

Post by John Lemo » Tue, 18 May 2004 07:24:44



I've got reverse DNS configured on my windows 2000 server...



However when doing NSLOOKUP (and other reverse-DNS based tools) on this
address from an internet client, it only works when the client is explicitly
pointing to this server as the primary DNS server.



When querying from an internet client that is NOT pointing to this server as
the primary DNS server, the message returned by nslookup is "can't find
xxx.xxx.xxx.xxx: Non-existent domain".



BTW, forward DNS is working like a champ.



Any suggestions?
 
 
 

reverse DNS lookup problem

Post by Kevin D. G » Tue, 18 May 2004 10:07:20


John Lemon < XXXX@XXXXX.COM > posted a question
Then Kevin replied below:

Since you obscured the IP address, can I assume you are talking about the
reverse lookup on your public IP address?
Unless your ISP, who actually owns the IP address, has delegated the reverse
lookup to your DNS server, your DNS server will not be queried for the PTR
record.
You will need to contact your ISP, or whomever is Authoritative for the
reverse lookup, to delegate it to you or create the PTR for you.

--
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.
==========================================
http://www.yqcomputer.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://www.yqcomputer.com/ ~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.yqcomputer.com/
==========================================

 
 
 

reverse DNS lookup problem

Post by Herb Marti » Tue, 18 May 2004 11:52:48

Kevin, pretty much covered it but the chances are you used an
IP address that is NOT delegated from a (valid) parent zone.

You said, "Internet client" -- such machines are configured to
resolve through the DNS servers on the Internet (one supposes)
and so to find "your reverse zone" it must be delegated at the
parent (reverse zone.)

If these are internal DNS clients (that also need Internet resolution)
then you really should point them to INTERNAL DNS servers
when then resolve internal addresses (and reverses) locally and
use "Forwarding" to resolve addresses on the Internet.