Searching for 205.216.108.208.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 108 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 99 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 99 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 100 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 101 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 110 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 127 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 119 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 111 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 125 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 126 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 114 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 127 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 110 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 111 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for u.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for u.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 17 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 17 msSearching for u.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 17 ms
Searching for ns4.oar.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns4.oar.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns4.oar.net. A record at ns7.oar.net. [206.244.199.2] ...took 101 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2]
...took 102 msSearching for ns4.oar.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns4.oar.net. A record at ns7.oar.net. [206.244.199.2] ...took 101 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 108 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 99 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 99 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 99 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 100 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 101 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 110 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 127 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 119 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 111 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 125 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 126 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 103 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 114 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 127 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns6.oar.net. [157.134.199.2] ...took 110 ms
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns5.oar.net. [199.218.199.2] ...took 102 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns7.oar.net. [206.244.199.2] ...took 111 ms
SERVFAIL
Searching for 205.216.108.208.in-addr.arpa. PTR record at ns4.oar.net. [199.18.199.2] ...took 102 ms
Too many delegations to other servers. Probably a loop.
Total elapsed query time: 4,026 ms
