Searching for 63.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 63.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 95 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 181 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 175 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 95 ms
Searching for y.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for y.arin.net. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 91 ms
Searching for 63.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 l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 91 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 h.gtld-servers.net. [192.54.112.30] ...took 8 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 20 msSearching for ns1.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 8 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 181 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 175 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 63.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,224 ms