Searching for 10.220.48.80.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns1.rdi.pl. [109.199.15.3] Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=27081
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns2.rdi.pl. [109.199.16.3] Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=33178
Searching for 10.220.48.80.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for ns4.apnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns4.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 165 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at ns4.apnic.net. [202.12.31.53]
...took 16 msSearching for ns4.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 165 ms
Searching for ns2.tpnet.pl. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for ns2.tpnet.pl. A record at d-dns.pl. [185.159.197.48] ...took 15 ms
Searching for ns2.tpnet.pl. A record at ns4.corpnet.pl. [80.50.50.180] ...took 38 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at ns2.tpnet.pl. [80.50.50.150]
...took 37 msSearching for ns2.tpnet.pl. A record at d-dns.pl. [185.159.197.48] ...took 15 ms
Searching for ns2.tpnet.pl. A record at ns4.corpnet.pl. [80.50.50.180] ...took 38 ms
Searching for dns1.rdi.pl. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 34 ms
Searching for dns1.rdi.pl. A record at h-dns.pl. [185.159.198.48] ...took 6 ms
Searching for dns1.rdi.pl. A record at ns1.ogicom.pl. [94.152.255.103] ...took 34 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns1.rdi.pl. [109.199.15.3]
Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=706Searching for dns1.rdi.pl. A record at h-dns.pl. [185.159.198.48] ...took 6 ms
Searching for dns1.rdi.pl. A record at ns1.ogicom.pl. [94.152.255.103] ...took 34 ms
Searching for dns2.rdi.pl. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for dns2.rdi.pl. A record at d-dns.pl. [185.159.197.48] ...took 13 ms
Searching for dns2.rdi.pl. A record at ns1.ogicom.pl. [94.152.255.103] ...took 32 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns2.rdi.pl. [109.199.16.3]
Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=29936Searching for dns2.rdi.pl. A record at d-dns.pl. [185.159.197.48] ...took 13 ms
Searching for dns2.rdi.pl. A record at ns1.ogicom.pl. [94.152.255.103] ...took 32 ms
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns1.rdi.pl. [109.199.15.3] Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=27081
Searching for 10.220.48.80.in-addr.arpa. PTR record at dns2.rdi.pl. [109.199.16.3] Timed out while trying to resolve 10.220.48.80.in-addr.arpa./PTR, id=33178
None of the nameservers responded correctly.
Total elapsed query time: 8,798 ms