Searching for 4.116.200.207.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 6 ms
Searching for 4.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 264 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 294 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for u.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for u.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 4.116.200.207.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 6 msSearching for u.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns1.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns1.yahoo.com. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 11 msSearching for ns1.yahoo.com. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 264 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 4.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 294 ms
REFUSED
Searching for 4.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,366 ms