Searching for 128.168.242.92.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 128.168.242.92.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 15 ms
Searching for 128.168.242.92.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 15 ms
Searching for pri.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 13 ms
Searching for pri.authdns.ripe.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 5 ms
Searching for pri.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 199 ms
Searching for 128.168.242.92.in-addr.arpa. PTR record at pri.authdns.ripe.net. [193.0.9.5]
...took 12 msSearching for pri.authdns.ripe.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 5 ms
Searching for pri.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 199 ms
Searching for sf.idm.net.lb. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for sf.idm.net.lb. A record at r.ns.lb. [105.16.170.1] ...took 189 ms
Searching for sf.idm.net.lb. A record at ns0.idm.net.lb. [194.126.10.18] ...took 70 ms
Searching for 128.168.242.92.in-addr.arpa. PTR record at sf.idm.net.lb. [174.142.61.239]
...took 98 msSearching for sf.idm.net.lb. A record at r.ns.lb. [105.16.170.1] ...took 189 ms
Searching for sf.idm.net.lb. A record at ns0.idm.net.lb. [194.126.10.18] ...took 70 ms
Nameserver sf.idm.net.lb. reports: No such host 128.168.242.92.in-addr.arpa.
Total elapsed query time: 629 ms