Ten Ways to Solve DNS Problems (or: the web is amazing)
So I wrote about my woes with DNS, bemoaning how our VPS provider GleSYS's DNS servers were not performing well enough. As usual with the web, I was blown away by the feedback; not only did I get over a dozen tips on what to do, GleSYS themselves chimed in to say they've fixed the problem.
Either that's a PR move on their part, or their technicians are very attentive. I'd like to think the latter. So without further ado, here are the ten ways in which to solve the case of the slow DNS look-up:
- Google Public DNS
- Twisted Names
- blog about it
- pray for rain
There are of course pros and cons to every single one of these options above, and I'll just quickly address some obvious questions.
First up, BIND. As much as I love ISC software, BIND feels a little too heavy-duty for a one-off thing like this.
djbdns is, I'm sure, quality software too; here the problem is deployment. For djbdns, "integrating with the OS" means "write your own rc replacement and shove it down people's throats". I refer of course to the bane that is daemontools. I gave it a shot with qmail, never ever again.
As for OpenDNS and Google Public DNS, I'd have to benchmark them over a week or so to know what to think of them. However I'd much prefer to do business with people who will be accountable for downtime.
By far the most interesting of them is Unbound, because of what it says on the box: a lightweight caching DNS server.
For now it looks like GleSYS have fixed things on their end; if this becomes a problem again, it might be better to change VPS provider.