Searching for 170.161.100.92.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for 170.161.100.92.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 283 ms
Searching for 170.161.100.92.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 283 ms
Searching for ns3.lacnic.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for ns3.lacnic.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns3.lacnic.net. A record at ns4.lacnic.net. [190.112.52.35] ...took 170 ms
Searching for 170.161.100.92.in-addr.arpa. PTR record at ns3.lacnic.net. [200.3.13.14]
...took 199 msSearching for ns3.lacnic.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns3.lacnic.net. A record at ns4.lacnic.net. [190.112.52.35] ...took 170 ms
Searching for ns2.ptn.ru. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for ns2.ptn.ru. A record at b.dns.ripn.net. [194.85.252.62] ...took 50 ms
Searching for ns2.ptn.ru. A record at ns2.ptn.ru. [188.128.82.235] ...took 45 ms
Searching for 170.161.100.92.in-addr.arpa. PTR record at ns2.ptn.ru. [188.128.82.235]
...took 83 msSearching for ns2.ptn.ru. A record at b.dns.ripn.net. [194.85.252.62] ...took 50 ms
Searching for ns2.ptn.ru. A record at ns2.ptn.ru. [188.128.82.235] ...took 45 ms
Nameserver ns2.ptn.ru. reports: No such host 170.161.100.92.in-addr.arpa.
Total elapsed query time: 957 ms