Searching for 135.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 135.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 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 ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for x.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 29 ms
Searching for x.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for x.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 ms
Searching for 135.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 90 msSearching for x.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for x.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 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 d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
Searching for 135.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 d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 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 ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 135.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 135.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,418 ms