reverse resolution failing

[Chuck Swiger]

Hi--

On Apr 10, 2013, at 1:07 PM, Jim Pazarena wrote:
> So I have another domain which will not reverse resolve for me:
> 
> mail.tysers.com which also appears to be:
> mail.tyser.co.uk
> 
> 80.169.188.226
> 
> the IP, will not reverse resolve (for me) yet, once again,
> google (8.8.8.8) CAN RESOLVE IT.
> 
> On my original post, Tony Finch advised "the nameservers for
> the target are very broken".
> 
> But why is it that google can STILL resolve it?
> Do they have some special setting which pushes thru poorly
> configured DNS?

Nope, colt.net simply has only one out of three listed nameservers
working well enough to return an answer rather than NXDOMAIN:

% dig -x 80.169.188.226 @ns2.colt.net
[ ... ]
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26181
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 0

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

;; ANSWER SECTION:
226.188.169.80.in-addr.arpa. 86400 IN	PTR	mail.tysers.com.
226.188.169.80.in-addr.arpa. 86400 IN	PTR	mail.tyser.co.uk.

;; AUTHORITY SECTION:
169.80.in-addr.arpa.	86400	IN	NS	ns4.colt.net.
169.80.in-addr.arpa.	86400	IN	NS	ns2.colt.net.
169.80.in-addr.arpa.	86400	IN	NS	ns3.colt.net.

% dig -x 80.169.188.226 @ns3.colt.net
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21747
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
169.80.in-addr.arpa.	86400	IN	SOA	ns2.colt.net. eudnsmaster.colt.net. 2013044938 10800 3600 604800 86400

% dig -x 80.169.188.226 @ns4.colt.net
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2133
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
169.80.in-addr.arpa.	86400	IN	SOA	ns2.colt.net. eudnsmaster.colt.net. 2013044938 10800 3600 604800 86400

> Is there anything I can do to MY named to get this working?

Yes and no.  You could claim to be authoritative for the reverse zone,
but that won't fix it for anyone else.  Get colt.net to fix their broken DNS servers.

Regards,
-- 
-Chuck