Reverse DNS problems

[Mark Andrews]

> On 20 Mar 2004 at 8:06, 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:06:43 +1100
> > 
> > > On 18 Mar 2004 at 15:33, John Emery wrote:
> > > To:             	comp-protocols-dns-bind at isc.org
> > > From:           	John Emery <nospam_john_nospam at suemills.com>
> > > Subject:        	Re: Reverse DNS problems
> > > Date sent:      	Thu, 18 Mar 2004 15:33:15 -0800
> > > Organization:   	Epoch Internet
> > > 
> > > > Cheers,
> > > > 
> > > > I'm not entirely sure I understand your hints completely, but they did 
> > > > lead me down the right path.  I think I've got the issue resolved.  The
>  
> > > > mail host I've been having trouble sending mail to due to this reverse 
> > > > DNS issue, is accepting mail from OUR mail host now.
> > > 
> > > Your reverse records should not have an 'alias'.
> > 
> > 	Again you are wrong.  In this case more so because you failed
> > 	to read RFC 2317.
> 
> 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.  

	Well if you delegate each individual address you don't need CNAMES.

> > > > I'm still battling with my ISP over whos responsibility it is to remove
>  
> > > > that defunct server from the reverse list.
> > > 
> > > There is no battle ... If you have authority for your domain server it is
>  
> > > YOUR responsibility. Don't see the problem though ... just remove the 
> > > entry from the reverse zone.
> >  
> > 	Removing the A record is his responsability (via network solutions).
> > 	Removing the NS record in the ISP's responsability.
> 
> He indicated he ran his own server in which case he should control the ns 
> records.

	And his copy was correct.  The delegation however was and still
	is wrong.  To get this corrected he needs to contact is ISP.

	The forward delegation still needs to be fixed which means
	contacting Network Solutions.

	Mark
 
0-26.171.135.206.in-addr.arpa. 14400 IN NS      hydrogen.suemills.com.
0-26.171.135.206.in-addr.arpa. 14400 IN NS      horogw.suemills.com.
;; Received 135 bytes from 205.214.45.6#53(auth1.ns.eni.net) in 762 ms

; <<>> DiG 9.2.3 <<>> ns 0-26.171.135.206.in-addr.arpa @hydrogen.suemills.com
;; ANSWER SECTION:
0-26.171.135.206.in-addr.arpa. 10800 IN	NS	hydrogen.suemills.com.

horogw.suemills.com.    172800  IN      A       206.135.171.2
suemills.com.           172800  IN      NS      hydrogen.suemills.com.
suemills.com.           172800  IN      NS      ns2.suemills.com.
;; Received 126 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 244 ms

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org