Searching for 254.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for 254.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 281 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 281 ms
Searching for y.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 15 ms
Searching for y.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 91 ms
Searching for 254.116.200.207.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 7 msSearching for y.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 91 ms
Searching for ns4.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 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 ns4.yahoo.com. [98.138.11.157] ...took 120 ms
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 129 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 ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 254.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,530 ms