Searching for 134.202.244.106.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 134.202.244.106.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 252 ms
Searching for 134.202.244.106.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 252 ms
Searching for ns3.lacnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns3.lacnic.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns3.lacnic.net. A record at lacnic.authdns.ripe.net. [193.0.9.11] ...took 11 ms
Searching for 134.202.244.106.in-addr.arpa. PTR record at ns3.lacnic.net. [200.3.13.14]
...took 199 msSearching for ns3.lacnic.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns3.lacnic.net. A record at lacnic.authdns.ripe.net. [193.0.9.11] ...took 11 ms
Searching for d.dns.kr. A record at G.ROOT-SERVERS.NET. [192.112.36.4]
...took 26 ms
Searching for d.dns.kr. A record at g.dns.kr. [202.31.190.1] ...took 7 ms
Searching for 134.202.244.106.in-addr.arpa. PTR record at d.dns.kr. [203.83.159.1]
...took 248 msSearching for d.dns.kr. A record at g.dns.kr. [202.31.190.1] ...took 7 ms
Nameserver d.dns.kr. reports: No such host 134.202.244.106.in-addr.arpa.
Total elapsed query time: 783 ms