[dns-operations] problem reverse dns resolve 18.104.22.168
jeroen at unfix.org
Fri Jan 13 11:34:34 UTC 2012
On 2012-01-13 12:12 , Michael Monnerie wrote:
> we have 2 DNS servers in 2 different datacenters, running since years
> without problem. So I think it's not a problem from us, that both our
> DNS cannot resolve a simple
> # dig -x 22.214.171.124
> We just get a timeout, but when I try from different internet accesses,
> I get a resolve:
> 126.96.36.199.in-addr.arpa. 86400 IN PTR vcoe-exchange.vcoe.at.
> Can someone show me where to search for the problem?
Use +trace, and you will find it quickly enough that:
dig +trace -x 188.8.131.52
228.186.212.in-addr.arpa. 86400 IN NS chans01.chello.fr.
228.186.212.in-addr.arpa. 86400 IN NS chans00.chello.fr.
;; Received 98 bytes from 184.108.40.206#53(220.127.116.11) in 417 ms
;; connection timed out; no servers could be reached
There is your answer as those don't answer
More information about the dns-operations