I want to start this article by saying that I am a big fan of OpenDNS and a lot of people that know me can tell you how many times I have recommended them to change their default DNS servers provided by their ISPs with OpenDNS ones. The main reason for this is speed, both in serving requests and in propagating changes through the Internet. Not a few times I was amazed to see that my ISP’s DNS servers wouldn’t hold on some records created in the last 6 hours but OpenDNS handles them in the first 15 minutes or so…
Other cool features are the ability to create shortcuts for your network (you need to register, free of charge) like pointing http://radu to http://radu.cotescu.com, customizing the error pages when records aren’t found, filtering the traffic for your network (denying access to porn, phishing, auctions, adware sites, etc.) and monitoring your network requests. For that you either have to register your static IP with your account or to use a dynamic IP client for updating your info on their servers.
But today the inevitable happened: OpenDNS failed to resolve the address of my blog. The sky collapsed (literally as Bucharest was under some thunderstorms). After some checking (they do provide a domain checkup on their servers with the option to manually refresh the info for the domains) I was stunned to see that the server from London doesn’t have any info for my domain. Strange. I then moved on to check their servers status (you can do that too) and there didn’t seem to be any problem, according to their info.
The trace stopped at one of OpenDNS servers. Mmmmkay. All I had to do was to wait. And I did. After one hour and a half everything went back to normal. Even so, I still recommend them because these accidents are extremely rare.