Searching for 130.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 130.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 5 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 5 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 b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 ms
Searching for 130.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 b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 ms
Searching for ns4.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 6 ms
Searching for ns4.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 210 ms
Searching for 130.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 b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 210 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 130.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,429 ms