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 272 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 272 ms
Searching for rirns.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for rirns.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for rirns.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 164 ms
Searching for 239.35.1.89.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53]
...took 94 msSearching for rirns.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for rirns.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 164 ms
Searching for ns3.netcologne.de. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns3.netcologne.de. A record at z.nic.de. [194.246.96.1] ...took 6 ms
Searching for ns3.netcologne.de. A record at pns.dtag.de. [194.25.0.125] ...took 9 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 z.nic.de. [194.246.96.1] ...took 6 ms
Searching for ns3.netcologne.de. A record at pns.dtag.de. [194.25.0.125] ...took 9 ms
Nameserver ns3.netcologne.de. reports: No such host 239.35.1.89.in-addr.arpa.
Total elapsed query time: 607 ms