Playing with Debian

Tuesday, 26th February 2008 at 09:58pm

DNS servers are hard...

Tonight's post was going to be about setting up your own DNS server, using bind. Instead, tonight's post will be about how impossible it is, and that you should stick with your domain registrar. They'll usually handle your DNS for you anyway, for free.

As always, installing bind was easy. Setting it up was a bitch though.

I wanted to run the Shamess Productions home page from this server, as a secondary nameserver. Thankfully, I know my DNS host personally so I could talk to him about finding his hashkey for RNDC, but even then it was confusing. I'd imagine it to be almost imposible to get that from GoDaddy or someone.

And even with that, I still had no idea why I wasn't synchronising.

Honestly, there's better things you can do with your server's resources than run a DNS server.

I will cover this in detail some time later though, so stay tuned. (If I get inundated with comments ask how to do this, I'll do more research and get it up faster.)

In the meantime, stick with the DNS server of whoever you registered your domain. Just ask them to point an A record for your domain to the IP address of your server.

Comments

Your name: Your URL:

Body:

User comments

James says:

I've always found Bind to be a pain to set up, luckily I've always had control over both servers, or over the master which really does make things easier. Having to jump between configuring your slave and asking someone for a snippet of their masters config can only make things much more complicated. Mind you, once you do have Bind running, it's great.

Read some previous entries