Searching for 100.200.59.64.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 100.200.59.64.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 118 ms
Searching for 100.200.59.64.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 118 ms
Searching for z.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for z.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 139 ms
Searching for 100.200.59.64.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 96 msSearching for z.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 139 ms
Searching for ns2.fortdodgefiber.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns2.fortdodgefiber.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for 100.200.59.64.in-addr.arpa. PTR record at ns2.fortdodgefiber.net. [64.59.200.42]
...took 122 msSearching for ns2.fortdodgefiber.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns1dhq.name.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1dhq.name.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns1dhq.name.com. A record at woz.ns.cloudflare.com. [172.64.33.150] ...took 7 ms
Searching for ns2.fortdodgefiber.net. A record at ns1dhq.name.com. [163.114.216.17]
...took 31 msSearching for ns1dhq.name.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns1dhq.name.com. A record at woz.ns.cloudflare.com. [172.64.33.150] ...took 7 ms
Nameserver ns2.fortdodgefiber.net. reports: No such host 100.200.59.64.in-addr.arpa.
Total elapsed query time: 618 ms