Reverse DNS problems

[ngaccess at hotpop.com]

On 20 Mar 2004 at 8:02, Mark Andrews wrote:
To:             	ngaccess at hotpop.com
Copies to:      	comp-protocols-dns-bind at isc.org
From:           	Mark Andrews <Mark_Andrews at isc.org>
Subject:        	Re: Reverse DNS problems 
Date sent:      	Sat, 20 Mar 2004 08:02:10 +1100
> 
> > First:
> >    Domain servers in listed order:
> >    HYDROGEN.SUEMILLS.COM        206.135.171.2
> >    HOROGW.SUEMILLS.COM          64.218.226.140
> > 
> > Goto networksolutions and login to your dns management and delete the 
> > host HOROGW.SUEMILLS.COM (or whatever they require you to do) and you 
> > need to add a second server for redundancy. (FWIW, your ISP is correct in 
> > saying they can't do it)
> > 
> > Next:
> > 2.171.135.206.in-addr.arpa.
> >     alias = 2.0-26.171.135.206.in-addr.arpa.
> > 2.0-26.171.135.206.in-addr.arpa.
> >     host = hydrogen.suemills.com.
> > 
> > This should simply be:
> > 2.171.135.206.in-addr.arpa.
> >     host = hydrogen.suemills.com.
> 
> 	You are *wrong*.  Go read RFC 2317 to understand what is
> 	being done here.

Okay, okay ... (duck and cover)

I have been using many small blocks of 8 and 16 ips and never use all 
that - just a ptr and the host shows on reverse without any 'alias' ...
I picked up on that as I thought you were never to use cname with mx 
records but I concur as I was not even aware of that.  

> 
> > Then:
> > 3.171.135.206.in-addr.arpa.
> >     alias = 3.0-26.171.135.206.in-addr.arpa.
> > 3.0-26.171.135.206.in-addr.arpa.
> >     host = radon.suemills.com.
> > 
> > This is your mx record which there again should simply be:
> > 3.171.135.206.in-addr.arpa.
> >     host = radon.suemills.com.
> 
> 	Again you are wrong.

See above ...