Super-slow Dns Resolution?

[SurfRider]

.

In the past few days DNS resolution of domain links has been the slowest I've ever seen anywhere. Sometimes as much as 30 to 60 seconds to resolve something as basic as www.google.co.th

My DNSCache has only 24 references and none are common domains, so something is apparently wrong there.

I have CAT DSL on a dedicated 2Mbps line and DNS resolution generally has always been very fast.

Is it possible that Big-Thai-Brother is once again trapping and sniffing every DNS request to make sure that we're all being good little girls and boys, or could this simply be a technical glitch?

If anyone has any suggestions for the IPs of DNS servers that you think are resolving normally and don't mind sharing them, please post the IPs

Any comments, suggestions, or potential solutions are most welcome.

.

[trogers]

You can use this DNS tester to check the performance of your ISP's DNS servers:

http://www.grc.com/dns/benchmark.htm

Also, try flushing your DNS cache:

http://www.tech-faq.com/flush-dns.shtml

DNS servers of True Internet:

203.144.207.29

203.144.207.49

[SurfRider]

.

Trogers,

Thanks for the suggestions. The "DNS Benchmark" App flagged the secondary CAT DNS server as dead. I replaced it with the 1st TRUE DNS IP that you posted, but it sees that as dead also. Likewise, the 2nd TRUE DNS IP.

So it appears that we have either three dead DNS servers ( not likely ) or Benchmark is not processing secondary DNS references properly -OR- TRUE has their DNS servers reserved for TRUE customers only and blocks any incoming access attempts from outside their network.

DNS Resolution is still as slow as molasses, but GRC explains why:

"One or more of this system's 2 nameservers are dead!

Although the whole point of having multiple redundant DNS resolving name-servers is to have a reliable source of DNS lookups, any name-servers that actually are dead and not replying to DNS queries can seriously hamper a system's performance as it waits for the dead name-server to reply before trying to use its backup name-servers. Therefore, removing any persistently dead name-servers is always a good idea."

I'll attempt to get CAT's suggestions for DNS IPs, but if you've ever dealt with CAT, you'll know that I might need to send them a tutorial via snail-mail in Thai explaining what DNS means

If anyone has a non-secret DNS IP that I can test, please post it.

Thanks...

.

[trogers]

Perhaps you can use OpenDNS servers temporarily until your ISP resolve their problem.

208.67.222.222

208.67.220.220

http://www.opendns.com/

[Supernova]

I use Level 3 and Speakeasy DNS servers as backup. You can find them here along with a dozen others to choose from.

[SurfRider]

.

Thanks very much to everyone for all the suggestions!

That Benchmark App is quite a gadget! I was able to weed out the dead CAT DNS server and pair the remaining one with the fastest safe DNS server that Benchmark found.

The other server suggestions worked also, but didn't result in a very high Benchmark score, so I went with the fastest safe pair for now.

There appears to be at least some intermittent improvement in some DSN resolutions, but still not quite up to the standard that existed before the problem started. I'll continue to run Benchmark to keep on top of the situation.

.