Dec 29 2007
DNS Suckage
My ISP (Rogers) has had increasingly unreliable DNS servers for some time now.
I called their tech support line about the issue a few weeks back since there was one site in specific that seemed to be a chronic issue, but as I somehow expected the level one tech support person was only vaguely aware of what DNS was in the first place. Of course, the usual procedure ensued - they try the website on their end, and if it loads, there is no problem, right?
I suppose I could have pushed the matter, or if I really wanted to express my displeasure, change ISP’s because of it, but it didn’t seem worth fighting about.
Instead, I switched to OpenDNS and left my ISP’s DNS servers as only a third-level emergency backup.
The setup was of course, simple - I simply changed my routers default DNS settings, refreshed, and everything was up and running.
In addition to being much more reliable (all my formerly problematic sites now load reliably) it also has a great many extra features that have already become a great plus to me, the primary one being content filtering.
When I upgraded our Mac’s to Leopard I was looking forward to using the account level parental filters for when our kids (ages 7 and 10) are surfing, but after utilizing the “Approved Websites Only” option for a month, I eventually had to downgrade to the “Attempt to block adult content” option instead. The Approved-Only option was a great feature, but a few websites that the kids were using were full of URL jumps (many with a wide array of IP based addresses, presumably a load-spreading tactic) which made the approved-only option a lesson in frustration - every time one of the sites in question jumped to a different IP address, Leopard would pop up a window seeking administrator approval.
Sometimes this would persist 6 or 8 times in a row before the site would function again, only to repeat the next time the kids logged in. There is apparently no way to approve an IP range, only physical domain names, so it was tedious.
Clearly, this wasn’t going to work, so now the accounts are set at the “block adult material” setting instead. This means that websites will reliably work again, but it also means that allot of websites that I don’t want the kids to have access to in the first place are now once again accessible.
Typically our kids are well behaved on the computers, and they are in public areas of the house, but none the less, I still believe in filtering what children that age are allowed to see on the ‘Net.
I blocked a few via the router, but it has an expectedly limiting filtering system.
OpenDNS on the other hand not only provides a reliable DNS server once again, but provides a multitude of filtering and content control that is adjustable via my account page.
Works for me.