Searching for 134.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for 134.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
Searching for z.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for z.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 150 ms
Searching for 134.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 90 msSearching for z.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 150 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 d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 128 msSearching for ns4.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 134.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,482 ms