Searching for 239.35.1.89.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 301 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 301 ms
Searching for ns3.lacnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns3.lacnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 21 ms
Searching for ns3.lacnic.net. A record at lacnic.authdns.ripe.net. [193.0.9.11] ...took 11 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at ns3.lacnic.net. [200.3.13.14]
...took 201 msSearching for ns3.lacnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 21 ms
Searching for ns3.lacnic.net. A record at lacnic.authdns.ripe.net. [193.0.9.11] ...took 11 ms
Searching for ns3.netcologne.de. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns3.netcologne.de. A record at l.de.net. [77.67.63.105] ...took 14 ms
Searching for ns3.netcologne.de. A record at ns1.netcologne.de. [194.8.194.70] ...took 12 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at ns3.netcologne.de. [194.8.197.10]
...took 10 msSearching for ns3.netcologne.de. A record at l.de.net. [77.67.63.105] ...took 14 ms
Searching for ns3.netcologne.de. A record at ns1.netcologne.de. [194.8.194.70] ...took 12 ms
Nameserver ns3.netcologne.de. reports: No such host 239.35.1.89.in-addr.arpa.
Total elapsed query time: 614 ms