Searching for 135.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 12 ms
Searching for 135.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 151 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 115 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 193 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 151 ms
Searching for y.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 11 ms
Searching for y.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 148 ms
Searching for 135.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 j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 148 ms
Searching for ns2.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 11 ms
Searching for ns2.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns2.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16]
...took 5 msSearching for ns2.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns2.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 115 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 193 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,414 ms