reverse resolution failing

Jim Pazarena bind at paz.bz
Wed Apr 10 20:07:14 UTC 2013


Jim Pazarena wrote, On 2013-02-07 9:31 AM:
> my named is 9.9.0
>
> while it can resolve "webmail.acrodex.com" ( 139.142.184.10 )
>
> it cannot reverse resolve 139.142.184.10
>
> (example follows).
> However, if I do a simply nslookup using goodle DNS.
> nslookup 139.142.184.10 8.8.8.8
> IT WORKS!

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?
Is there anything I can do to MY named to get this working?


More information about the bind-users mailing list