Searching for 66.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 66.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 210 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 217 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
Searching for arin.authdns.ripe.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for arin.authdns.ripe.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for 66.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 m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for ns3.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 154 msSearching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 210 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 217 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 66.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 66.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,347 ms