Searching for 106.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 106.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 122 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 122 ms
Searching for y.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for y.arin.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for 106.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 h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for y.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for ns5.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns5.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 187 msSearching for ns5.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 106.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,357 ms