Searching for 249.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for 249.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 96 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 138 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 96 ms
Searching for u.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for u.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 89 ms
Searching for 249.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 b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 89 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 j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 13 msSearching for ns1.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 249.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 138 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,418 ms