Reverse DNS (PTR)

[BOG]

Greetings,
 You haven't given anyone that might want to help *any* information to work
with. Do you have a domain name? Have you setup DNS for the domain name?
What DNS server software do you use? How large a net block are you responsible
for? If you are using BIND, have you setup your zones for:
loclahost?
localhost.rev?
yourdomain.dom.zone?
yourdomain.dom.rev?
hint (.)?
These are fundamental prerequesits. Without any of these details, how could
*anyone* hope to assist you? You must ask yourself what information might
someone need *prior* to posting questions/ plea's for help. That way, you
can be sure that those who wish to assist you have the tools to guide you
to a solution.

Best wishes.


"Shabam" <blislecp at hotmail.com> wrote in message news:<cetpns$vcc$1 at sf1.isc.org>...
> 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?