Searching for 45.98.72.67.in-addr.arpa. PTR record at A.ROOT-SERVERS.NET. [198.41.0.4]
...took 7 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 94 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns1.propel.com. [162.198.209.91] Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=28233
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns2.propel.com. [67.72.98.64] Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=20739
Searching for 45.98.72.67.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 94 ms
Searching for z.arin.net. A record at C.ROOT-SERVERS.NET. [192.33.4.12]
...took 11 ms
Searching for z.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 101 msSearching for z.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for ns2.level3.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for ns2.level3.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 34 ms
Searching for ns2.level3.net. A record at ns2.l3.net. [209.244.0.2] ...took 21 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns2.level3.net. [209.244.0.2]
...took 23 msSearching for ns2.level3.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 34 ms
Searching for ns2.level3.net. A record at ns2.l3.net. [209.244.0.2] ...took 21 ms
Searching for ns1.propel.com. A record at J.ROOT-SERVERS.NET. [192.58.128.30]
...took 34 ms
Searching for ns1.propel.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns1.propel.com. [162.198.209.91]
Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=42643Searching for ns1.propel.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for ns-2038.awsdns-62.co.uk. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for ns-2038.awsdns-62.co.uk. A record at dns4.nic.uk. [43.230.48.1] ...took 12 ms
Searching for ns-2038.awsdns-62.co.uk. A record at g-ns-1218.awsdns-62.co.uk. [205.251.196.194] ...took 22 ms
Searching for ns1.propel.com. A record at ns-2038.awsdns-62.co.uk. [205.251.199.246]
...took 11 msSearching for ns-2038.awsdns-62.co.uk. A record at dns4.nic.uk. [43.230.48.1] ...took 12 ms
Searching for ns-2038.awsdns-62.co.uk. A record at g-ns-1218.awsdns-62.co.uk. [205.251.196.194] ...took 22 ms
Searching for ns2.propel.com. A record at C.ROOT-SERVERS.NET. [192.33.4.12]
...took 11 ms
Searching for ns2.propel.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns2.propel.com. [67.72.98.64]
Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=8813Searching for ns2.propel.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for ns-573.awsdns-07.net. A record at C.ROOT-SERVERS.NET. [192.33.4.12]
...took 11 ms
Searching for ns-573.awsdns-07.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns-573.awsdns-07.net. A record at g-ns-1351.awsdns-07.net. [205.251.197.71] ...took 22 ms
Searching for ns2.propel.com. A record at ns-573.awsdns-07.net. [205.251.194.61]
...took 6 msSearching for ns-573.awsdns-07.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns-573.awsdns-07.net. A record at g-ns-1351.awsdns-07.net. [205.251.197.71] ...took 22 ms
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns1.propel.com. [162.198.209.91] Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=28233
Searching for 45.98.72.67.in-addr.arpa. PTR record at ns2.propel.com. [67.72.98.64] Timed out while trying to resolve 45.98.72.67.in-addr.arpa./PTR, id=20739
None of the nameservers responded correctly.
Total elapsed query time: 8,702 ms