Searching for 250.27.247.43.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 250.27.247.43.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 172 ms
SERVFAIL
Searching for 250.27.247.43.in-addr.arpa. PTR record at ns06.mtel.mo. [103.237.126.4] ...took 326 ms
SERVFAIL
Searching for 250.27.247.43.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 172 ms
Searching for ns1.apnic.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for ns1.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns1.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 11 ms
Searching for 250.27.247.43.in-addr.arpa. PTR record at ns1.apnic.net. [203.119.42.53]
...took 188 msSearching for ns1.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns1.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 11 ms
Searching for ns06.mtel.mo. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 12 ms
Searching for ns06.mtel.mo. A record at d.monic.mo. [202.175.51.115] ...took 279 ms
Searching for 250.27.247.43.in-addr.arpa. PTR record at ns06.mtel.mo. [103.237.126.4]
...took 301 msSearching for ns06.mtel.mo. A record at d.monic.mo. [202.175.51.115] ...took 279 ms
Searching for ns03.mtel.net.mo. A record at I.ROOT-SERVERS.NET. [192.36.148.17]
...took 11 ms
Searching for ns03.mtel.net.mo. A record at a.monic.mo. [202.175.87.47] ...took 280 ms
Searching for ns03.mtel.net.mo. A record at ns03.mtel.net.mo. [103.237.126.3] ...took 298 ms
Searching for ns06.mtel.mo. A record at ns03.mtel.net.mo. [103.237.126.3]
...took 321 msSearching for ns03.mtel.net.mo. A record at a.monic.mo. [202.175.87.47] ...took 280 ms
Searching for ns03.mtel.net.mo. A record at ns03.mtel.net.mo. [103.237.126.3] ...took 298 ms
SERVFAIL
Searching for 250.27.247.43.in-addr.arpa. PTR record at ns06.mtel.mo. [103.237.126.4] ...took 326 ms
SERVFAIL
None of the nameservers responded correctly.
Total elapsed query time: 2,247 ms