IDNet's caching DNS servers seem to be struggling looking up .com addresses in a timely manner. Was getting slow DNS looking up a lot of webpages I frequent, so I tested it out using nslookup
First using IDNet's caching DNS.
> www.goat.com
Server: resolver0.idnet.net
Address: 212.69.36.3
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
ipconfig /flushdns was then performed and DNS was then retested using the only other DNS I can remember off the top of my head, which happens to be Plusnet's server.
> www.goat.com
Server: [195.166.128.16]
Address: 195.166.128.16
Non-authoritative answer:
Name: www.goat.com
Address: 72.3.135.150
I performed this www.randomanimal.com test several times with the similar results - although occasionally the IDnet DNS did come back within 2 seconds.
So my question is 'What's wrong with the IDNet resolvers?'
I can ping them fine with no packet loss and my internet connection is otherwise very rapid in upload and download.
Answers on a postcard. Or preferably here.
Cheers
I'm not aware of a problem, but there's no reason why I would be. I have tried switching to OpenDNS but couldn't detect a difference.
I would suggest, therefore, that you drop support an email (or ring them Monday).
Sorry. :(