Reverse DNS not working for new server

[Stephen John Smoogen]

On 11/26/06, dhottinger at harrisonburg.k12.va.us
<dhottinger at harrisonburg.k12.va.us> wrote:
> I added a new webmail server several weeks ago.  I made the pert. DNS
> entries to the zone file and the reverse lookup file.  Within my
> domain using my DNS servers everything resolves correctly.  When I do
> an nslookup for 204.111.40.8 I get newproxy.harrisonburg.k12.va.us.
> However, outside my domain I get
> UnKnown can't find 204.111.40.10: Non-existent domain.  Now the rest
> of my ip's resolve correctly.  Heres my zone file:
>

I think it is because to the reverse DNS tree.. you don't own those ip
addresses, but your ISP:Shentel Service Company  does. So when a
reverse lookup occurs it is going to their DNS server:
ns2.shentel.net. [dig +trace -x 204.111.40.10].

Unless you have a Class C or your ISP is using classless reverse
delegation, they will always maintain the reverse numbers as tracked
by the outside world.

-- 
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"