Shaw DNS Issues? (Resolved, changed DNS servers)

[Tom]

Okay, I resolved it by using Google Public DNS

For Tonnica's sake (who is likely having this problem as well) here's a quick "how to"
http://code.google.com/speed/public-dns/docs/using.html

Here's irony for ya:

I just REMOVED my Google DNS -- because since the IP change, I couldn't "find" the RW domain anymore.

Weird eh?

I guess Shaw's not as bad as I thought it was, when I made the switch I coulda sworn I noticed a speed increase, now not so sure...




also, this:

I have tested google dns but went back to my local shaw dns because the latancy was horrid.

Yeah, it seems google is cacheing for far too long. Shaw will cache for a few hours to a day. But shaw's DNS likes to get slow, or just be down fairly often.

I've pretty much switched to running my own DNS server.

[Lazybones]

If you don't like your ISPs DNS you can always run your own... I think it is better than using those 3rd party DNS providers like OpenDNS and Google since I find their latency so poor.

[Tom]

If you don't like your ISPs DNS you can always run your own... I think it is better than using those 3rd party DNS providers like OpenDNS and Google since I find their latency so poor.

Oh, one other thing that tends to effect speeds, especially with google. I tried using the DNS server setup on my new dedicated server (its in michigan), and it turns out I got google servers with much higher latencies than if I used shaw's or my own. Some how they are doing geo localization by DNS server, rather than your own. I thought they only picked the server based on your own ip, seems they don't.