Reverse DNS (PTR)

Stuart Wallace Stuart at nildram.net
Thu Aug 5 17:15:29 UTC 2004


That will most likely be because your IP range does not have nameservers
assigned at the IP registry, be that ARIN, RIPE etc or whatever.

Try doing an nslookup against the IP provider nameservers and see what
results you get...

Stuart Wallace
Nildram Ltd

> -----Original Message-----
> From: Shabam [mailto:blislecp at hotmail.com] 
> Sent: 01 August 2004 06:41
> To: comp-protocols-dns-bind at isc.org
> Subject: Reverse DNS (PTR)
> 
> I was informed by Aol that emails from my domain isn't 
> reaching aol subscribers because of the lack of PTR (reverse 
> DNS).  I did configure it in my DNS server.  When within the 
> server and I type my site's IP address it returns the domain 
> name just fine.  However when I'm doing a nslookup from 
> outside I get this:
> 
> ---------------------------------------------
> [root at somewhereelse]# nslookup 1.2.3.4
> Note:  nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead.  Run 
> nslookup with the `-sil[ent]' option to prevent this message 
> from appearing.
> Server:         127.0.0.1
> Address:        127.0.0.1#53
> 
> ** server can't find 4.3.2.1.in-addr.arpa: NXDOMAIN
> ---------------------------------------------
> 
> Here's the output when doing the same within the DNS server 
> that's delegated to the domain name in question:
> 
> ---------------------------------------------
> [root at dnsserver]# nslookup 1.2.3.4
> Answer crypto-validated by server:
> Server:  dnsserver.whatever.com
> Address:  1.2.3.1
> 
> Answer crypto-validated by server:
> Name:    www.whatever.com
> Address:  1.2.3.4
> ---------------------------------------------
> 
> How do I fix this problem so nslookup works from outside the box?
> 
> 
> 
>  
> 
 



More information about the bind-users mailing list