Hostname or IP
Type
Searching for 217.123.157.220.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 20 ms
Searching for 217.123.157.220.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 116 ms
Searching for apnic.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 20 ms
Searching for apnic.authdns.ripe.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 21 ms
Searching for apnic.authdns.ripe.net. A record at manus.authdns.ripe.net. [193.0.9.7] ...took 12 ms
Searching for 217.123.157.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for dns6.kbtelecom.net.tw. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 20 ms
Searching for dns6.kbtelecom.net.tw. A record at d.dns.tw. [60.199.165.186] ...took 209 ms
Searching for dns6.kbtelecom.net.tw. A record at ns1.kbtelecom.net.tw. [61.63.0.66] ...took 401 ms
Searching for 217.123.157.220.in-addr.arpa. PTR record at dns6.kbtelecom.net.tw. [203.133.1.6] Timed out while trying to resolve 217.123.157.220.in-addr.arpa./PTR, id=32762
Searching for dns8.kbtelecom.net.tw. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 20 ms
Searching for dns8.kbtelecom.net.tw. A record at g.dns.tw. [34.141.111.176] ...took 6 ms
Searching for dns8.kbtelecom.net.tw. A record at ns1.kbtelecom.net.tw. [61.63.0.66] ...took 415 ms
Searching for 217.123.157.220.in-addr.arpa. PTR record at dns8.kbtelecom.net.tw. [203.133.1.8] Timed out while trying to resolve 217.123.157.220.in-addr.arpa./PTR, id=8480
Searching for 217.123.157.220.in-addr.arpa. PTR record at dns8.kbtelecom.net.tw. [203.133.1.8] Timed out while trying to resolve 217.123.157.220.in-addr.arpa./PTR, id=47276
Searching for 217.123.157.220.in-addr.arpa. PTR record at dns6.kbtelecom.net.tw. [203.133.1.6] Timed out while trying to resolve 217.123.157.220.in-addr.arpa./PTR, id=28002
None of the nameservers responded correctly.



Total elapsed query time: 9,274 ms
Dear Guest,
DNSWatch.info is available to anybody for free. This is only possible since we display ads to cover our expenses.
An ad blocker installed on your browser is blocking ads on DNSWatch.info.
Please turn off your ad blocker or use a different browser to access this page.