Searching for 27.163.231.94.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 19 ms
Searching for 27.163.231.94.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 170 ms
Searching for 27.163.231.94.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 170 ms
Searching for ns3.lacnic.net. A record at I.ROOT-SERVERS.NET. [192.36.148.17]
...took 11 ms
Searching for ns3.lacnic.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns3.lacnic.net. A record at ns.lacnic.net. [200.3.13.10] ...took 194 ms
Searching for 27.163.231.94.in-addr.arpa. PTR record at ns3.lacnic.net. [200.3.13.14]
...took 194 msSearching for ns3.lacnic.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns3.lacnic.net. A record at ns.lacnic.net. [200.3.13.10] ...took 194 ms
Searching for ns2.link-region.ru. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns2.link-region.ru. A record at e.dns.ripn.net. [193.232.142.17] ...took 5 ms
Searching for ns2.link-region.ru. A record at ns2.link-region.RU. [62.122.97.2] ...took 44 ms
Searching for 27.163.231.94.in-addr.arpa. PTR record at ns2.link-region.ru. [62.122.97.2]
...took 43 msSearching for ns2.link-region.ru. A record at e.dns.ripn.net. [193.232.142.17] ...took 5 ms
Searching for ns2.link-region.ru. A record at ns2.link-region.RU. [62.122.97.2] ...took 44 ms
Nameserver ns2.link-region.ru. reports: No such host 27.163.231.94.in-addr.arpa.
Total elapsed query time: 700 ms