Searching for 239.35.1.89.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 299 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 299 ms
Searching for rirns.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for rirns.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 21 ms
Searching for rirns.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53]
...took 92 msSearching for rirns.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 21 ms
Searching for rirns.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for ns1.netcologne.de. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1.netcologne.de. A record at f.nic.de. [81.91.164.5] ...took 6 ms
Searching for ns1.netcologne.de. A record at ns1.netcologne.de. [194.8.194.70] ...took 10 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at ns1.netcologne.de. [194.8.194.70]
...took 10 msSearching for ns1.netcologne.de. A record at f.nic.de. [81.91.164.5] ...took 6 ms
Searching for ns1.netcologne.de. A record at ns1.netcologne.de. [194.8.194.70] ...took 10 ms
Nameserver ns1.netcologne.de. reports: No such host 239.35.1.89.in-addr.arpa.
Total elapsed query time: 572 ms