Searching for 0.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 299 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 133 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 166 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 299 ms
Searching for y.arin.net. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for y.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 147 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 6 msSearching for y.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 147 ms
Searching for ns1.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 34 ms
Searching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns1.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 169 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 12 msSearching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns1.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 169 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 133 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 166 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,652 ms