Reverse DNS PTR

Tried posting this on comp.protocols.dns.bind like 3 times already but that
stupid "moderated" forum won't approve it for some reason. I'm so
frustrated. Anyways, I'm posting my question here in hopes that someone can
help. Thanks!

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@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@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?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Shabam" <blislecp@hotmail.com> writes:

>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:

You need to have the zone delegate to you. Usually, that has to be
handled by your ISP. Unless you own your own address range (had it
directly assigned), you will need to work with your ISP to solve this
problem.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (SunOS)

iD8DBQFBDbtPvmGe70vHPUMRAprhAKCrlZOAVPLsI8HLNVSetm WbbAO9BQCfX5N4
EhM8Uy+mRTwA8EU4zbCpA1A=
=MiHR
-----END PGP SIGNATURE-----

> The other method is to use the SMART_HOST option in your sendmail.mc
> macro file (I assume sendmail). What happens when you enable and
> configure the smart host option is that your box relays any smtp content
> to your isp's smtp server. Good documentation on this option is
> available via google searching. Other mta programs have something
> similar.

Thanks for the info but my servers are collocated and the IPs are dedicated,
so this will not work.

Shabam wrote:
>>The other method is to use the SMART_HOST option in your sendmail.mc
>>macro file (I assume sendmail). What happens when you enable and
>>configure the smart host option is that your box relays any smtp content
>>to your isp's smtp server. Good documentation on this option is
>>available via google searching. Other mta programs have something
>>similar.
>
>
> Thanks for the info but my servers are collocated and the IPs are dedicated,
> so this will not work.
>
In this case ask your hosting service to configure correctly the
sendmail they are providing. It's up to them to relay thru another
server or set-up reverse DNS etc.