Searching for 8.116.200.207.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 25 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 155 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 255 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 249 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 155 ms
Searching for u.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for u.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for u.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 146 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 12 msSearching for u.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for u.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 146 ms
Searching for ns4.yahoo.com. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 25 ms
Searching for ns4.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 6 ms
Searching for ns4.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 118 msSearching for ns4.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 6 ms
Searching for ns4.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 255 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 249 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,470 ms