Searching for 234.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 234.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
Searching for arin.authdns.ripe.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 201 ms
Searching for 234.116.200.207.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 11 msSearching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 201 ms
Searching for ns4.yahoo.com. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for ns4.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 121 msSearching for ns4.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 234.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,252 ms