Searching for 240.94.122.91.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for 240.94.122.91.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 168 ms
Searching for 240.94.122.91.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 168 ms
Searching for ns4.apnic.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for ns4.apnic.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 226 ms
Searching for 240.94.122.91.in-addr.arpa. PTR record at ns4.apnic.net. [202.12.31.53]
...took 16 msSearching for ns4.apnic.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 226 ms
Searching for ns2.ptn.ru. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for ns2.ptn.ru. A record at e.dns.ripn.net. [193.232.142.17] ...took 6 ms
Searching for ns2.ptn.ru. A record at ns1.ptn.RU. [213.59.199.163] ...took 37 ms
Searching for 240.94.122.91.in-addr.arpa. PTR record at ns2.ptn.ru. [188.128.82.235]
...took 45 msSearching for ns2.ptn.ru. A record at e.dns.ripn.net. [193.232.142.17] ...took 6 ms
Searching for ns2.ptn.ru. A record at ns1.ptn.RU. [213.59.199.163] ...took 37 ms
Nameserver ns2.ptn.ru. reports: No such host 240.94.122.91.in-addr.arpa.
Total elapsed query time: 640 ms
