Reverse DNS problems

[John Emery]

>>The Answer section gives "3.0-26.171.135.206.in-addr.arpa." as the host 
>>name.
> 
> 
> 	This is a RFC 2317 style delegation.
> 
> 	Rename your 171.135.206.in-addr.arpa zone to be
> 	0-26.171.135.206.in-addr.arpa.  You may need to
> 	fix zone contents.
> 
> 	Become a slave for 171.135.206.in-addr.arpa.

Thanks, so now that the new reverse zone seems to have propigated itself 
out onto other nameservers, digs output on a remote server that doesn't 
point to our NS gives this:

/root> dig -x 206.135.171.3

; <<>> DiG 9.2.2 <<>> -x 206.135.171.3
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49281
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;3.171.135.206.in-addr.arpa.    IN      PTR

;; ANSWER SECTION:
3.171.135.206.in-addr.arpa. 14400 IN    CNAME 
3.0-26.171.135.206.in-addr.arpa.
3.0-26.171.135.206.in-addr.arpa. 10800 IN PTR   radon.suemills.com.

;; AUTHORITY SECTION:
0-26.171.135.206.in-addr.arpa. 10800 IN NS      hydrogen.suemills.com.

;; Query time: 149 msec
;; SERVER: 209.253.113.2#53(209.253.113.2)
;; WHEN: Fri Mar 19 17:37:13 2004
;; MSG SIZE  rcvd: 120

/root>

I think this is right??

Or, this output from the host command:

/root> host 206.135.171.3
3.171.135.206.in-addr.arpa is an alias for 3.0-26.171.135.206.in-addr.arpa.
3.0-26.171.135.206.in-addr.arpa domain name pointer radon.suemills.com.
/root>

Our reverse lookup problem with the remote email host HAS been resolved, 
at least.

>>Well, horogw is no longer a valid host, nor is the IP one of ours. 
>>Since I can't think of anything else, seems to me that having this 
>>invalid host in the list could be causing the problem.
> 
> 
> 	You need to get the host record removed.  You need to
> 	contact your registrar, Network Solutions, to do this.
> 
> horogw.suemills.com.    172800  IN      A       64.218.226.140
> suemills.com.           172800  IN      NS      horogw.suemills.com.
> suemills.com.           172800  IN      NS      hydrogen.suemills.com.
> ;; Received 122 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 243 ms

I've removed horogw.suemills.com from the list of DNS servers for all 
the domains in our company.  I don't see it listed in the "authority" 
section whilest doing a reverse lookup anymore.  So, either the reverse 
zone record fix fixed it, or removing it from network solutions database 
fixed it, or both?

Thanks again...

John