We have to deal with DNS config through those paragons of virtue, hosting providers and (worse) domain name registration sites. I know, I'm tarring them all with the same brush but I don't think I've ever seen a site for name registration that doesn't make me feel slightly dirty for using it.
The underlying technology is pretty horrendously over-engineered, but it does have the excuse that it has been around for a long time, and when it was invented it was probably reasonable to assume that anyone who would ever have call to register or administer a domain would have a degree in computer science.
But it's even worse when those registration sites put a front end on it in the name of simplification.
|It may be true, but it's not as helpful as it could be.|
DNS config is made worse by the problem that it can allegedly take up to 48 hours for the internet to propagate your changes, so it's easy to think that a misconfiguration is, in fact, just a configuration waiting to propagate.
It wouldn't be hard to make a nice, easy-to-follow interface for common DNS config tasks.
- Instead of a complicated A and CNAME record grid, the user could answer simple questions like "What's the IP address of your server?", "What's the primary domain name for your site?", "What alternative names also point to the same site?", "Should this site work for the 'naked' domain example.com?"
- I wonder how much time has been spent globally on filling in the MX records for hosting your email on GMail - years, probably, for a task that could easily be automated on the basis of ticking a box that says "I'm using GMail". (Presumably the same is true of other email providers too, but I'm just a lot more familiar with GMail.)
Hell, for good measure it could even spit out some sample Apache / nginx config snippets too.