Re: reverse resolution failing

2013-04-10 Thread 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 RESOL

Re: reverse resolution failing

2013-04-10 Thread Matus UHLAR - fantomas
On 10.04.13 13:07, 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, Ton

Re: reverse resolution failing

2013-04-10 Thread Jim Pazarena
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 anot

Re: reverse resolution failing

2013-02-07 Thread Mark Andrews
In message , Warren Kumari wri tes: > Hmmm > > So, for many years I've wondered this. I've looked a little myself, and > spoken to a few folk, but never gotten a really satisfactory answer -- > maybe there just isn't one > > You often see freaky things like the above (actually, this one is onl

Re: reverse resolution failing

2013-02-07 Thread Warren Kumari
On Feb 7, 2013, at 12:51 PM, Tony Finch wrote: > Jim Pazarena wrote: >> >> while it can resolve "webmail.acrodex.com" ( 139.142.184.10 ) >> it cannot reverse resolve 139.142.184.10 > > They are using classless reverse DNS, which is fine except that the > nameservers for the target zone are ve

Re: reverse resolution failing

2013-02-07 Thread Mark Andrews
In message <20130207184127.ga23...@fantomas.sk>, Matus UHLAR - fantomas writes: > >Jim Pazarena wrote: > >> > >> while it can resolve "webmail.acrodex.com" ( 139.142.184.10 ) > >> it cannot reverse resolve 139.142.184.10 > > On 07.02.13 17:51, Tony Finch wrote: > >10.184.142.139.in-addr.arpa. CN

Re: reverse resolution failing

2013-02-07 Thread Matus UHLAR - fantomas
Jim Pazarena wrote: while it can resolve "webmail.acrodex.com" ( 139.142.184.10 ) it cannot reverse resolve 139.142.184.10 On 07.02.13 17:51, Tony Finch wrote: 10.184.142.139.in-addr.arpa. CNAME 10.0-25.184.142.139.in-addr.arpa. 0-25.184.142.139.in-addr.arpa. NS pluto.acrodex.com. 0-25.184.

Re: reverse resolution failing

2013-02-07 Thread Rich Goodson
tail end of dig +trace: 142.139.in-addr.arpa. 86400 IN NS ns1.clgrab.grouptelecom.net. 142.139.in-addr.arpa. 86400 IN NS ns2.toroon.grouptelecom.net. ;; Received 111 bytes from 199.71.0.63#53(199.71.0.63) in 153 ms 10.184.142.139.in-addr.arpa. 86400 IN CNAME 10.0-

Re: reverse resolution failing

2013-02-07 Thread Tony Finch
Jim Pazarena wrote: > > while it can resolve "webmail.acrodex.com" ( 139.142.184.10 ) > it cannot reverse resolve 139.142.184.10 They are using classless reverse DNS, which is fine except that the nameservers for the target zone are very broken. 10.184.142.139.in-addr.arpa. CNAME 10.0-25.184.142

Re: reverse resolution failing

2013-02-07 Thread Sten Carlsen
It does not resolve from my IP, probably there is no reverse entry. On 07/02/13 18:31, Jim Pazarena wrote: > 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

reverse resolution failing

2013-02-07 Thread Jim Pazarena
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! Can anyone suggest where I may be going wrong with this? my