Searching for 35.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for 35.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 265 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 300 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 266 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 265 ms
Searching for y.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for y.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 154 ms
Searching for 35.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 e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 154 ms
Searching for ns4.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 7 ms
Searching for ns4.yahoo.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 25 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 267 ms
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 116 msSearching for ns4.yahoo.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 25 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 267 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 300 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 266 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 35.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,962 ms