1 |
On Wed, Aug 17, 2011 at 3:56 PM, Grant <emailgrant@×××××.com> wrote: |
2 |
> I currently use a free service to host the DNS records for my website, |
3 |
> but I'm thinking of running a DNS server on the same machine that runs |
4 |
> my website instead. Would that be fairly trivial to set up and |
5 |
> maintain? If so, which package should I use? |
6 |
|
7 |
Just to counter all of the scary stories, I recently (within the past |
8 |
month or so) installed bind for the first time and set it up after a |
9 |
few days of googling around and reading docs. It seems to be working |
10 |
properly and securely, but I'd be lying if I said there wasn't a large |
11 |
amount of dumb luck, finger-crossing and hand-waving involved on my |
12 |
part to get it working. I have some familiarity with editing DNS zone |
13 |
files (on other people's servers) so I wasn't going into it completely |
14 |
blind. |
15 |
|
16 |
I don't know if I'd call it "fairly trivial", but with howto's and |
17 |
google at your fingertips you should be able to get it set up properly |
18 |
if you really want to. |
19 |
|
20 |
Usually the web-based DNS management by your domain name registrar or |
21 |
hosting provider are good enough for most "personal domain" kind of |
22 |
usage (like mine). In my case there was something that their web-based |
23 |
editor didn't support (TXT records on subdomains or something like |
24 |
that), and mostly because I just felt like trying to do it myself. |
25 |
Since they are my personal domains, nobody else will suffer if I break |
26 |
everything. Others are in the (lucky? not so lucky?) positions of |
27 |
administering systems where things actually have to work right the |
28 |
first time and all the time. :) |