1 |
Adding to success stories: |
2 |
|
3 |
I've deployed bind-9 on FreeBSD, Debian, and Arch. The most trouble |
4 |
was with Debian, what with the 'compositing trees' etc. The easiest |
5 |
was with FreeBSD. All three DNS servers are now in their eighth month |
6 |
of production, handling half of my company's NS needs. |
7 |
|
8 |
It's really not difficult. Complex, yes, but not difficult. With the |
9 |
help of http://www.zytrax.com/books/dns and the handbooks, I finished |
10 |
the FreeBSD and Arch installations in one day. (The Debian took |
11 |
another day of hair-pulling to understand HTF they put their |
12 |
compositing files together). |
13 |
|
14 |
One tip from me would be to prepare the DNS servers beforehand, test |
15 |
them, *then* ask the registrar to transfer the domain name to you. |
16 |
Like others have posted, most will require you to provide at least two |
17 |
authoritative NS. |
18 |
|
19 |
In my situation, I have 1 server in the cloud, and 2 servers in the |
20 |
company (responding to DNS requests via 2 different ISPs). |
21 |
|
22 |
That said, I might be installing a different NS for the 4th NS for |
23 |
diversity (i.e., prevent a single attack from disabling all 4 NS |
24 |
servers). |
25 |
|
26 |
Rgds, |
27 |
|
28 |
|
29 |
On 2011-08-18, Paul Hartman <paul.hartman+gentoo@×××××.com> wrote: |
30 |
> On Wed, Aug 17, 2011 at 3:56 PM, Grant <emailgrant@×××××.com> wrote: |
31 |
>> I currently use a free service to host the DNS records for my website, |
32 |
>> but I'm thinking of running a DNS server on the same machine that runs |
33 |
>> my website instead. Would that be fairly trivial to set up and |
34 |
>> maintain? If so, which package should I use? |
35 |
> |
36 |
> Just to counter all of the scary stories, I recently (within the past |
37 |
> month or so) installed bind for the first time and set it up after a |
38 |
> few days of googling around and reading docs. It seems to be working |
39 |
> properly and securely, but I'd be lying if I said there wasn't a large |
40 |
> amount of dumb luck, finger-crossing and hand-waving involved on my |
41 |
> part to get it working. I have some familiarity with editing DNS zone |
42 |
> files (on other people's servers) so I wasn't going into it completely |
43 |
> blind. |
44 |
> |
45 |
> I don't know if I'd call it "fairly trivial", but with howto's and |
46 |
> google at your fingertips you should be able to get it set up properly |
47 |
> if you really want to. |
48 |
> |
49 |
> Usually the web-based DNS management by your domain name registrar or |
50 |
> hosting provider are good enough for most "personal domain" kind of |
51 |
> usage (like mine). In my case there was something that their web-based |
52 |
> editor didn't support (TXT records on subdomains or something like |
53 |
> that), and mostly because I just felt like trying to do it myself. |
54 |
> Since they are my personal domains, nobody else will suffer if I break |
55 |
> everything. Others are in the (lucky? not so lucky?) positions of |
56 |
> administering systems where things actually have to work right the |
57 |
> first time and all the time. :) |
58 |
> |
59 |
> |
60 |
|
61 |
|
62 |
-- |
63 |
-- |
64 |
Pandu E Poluan - IT Optimizer |
65 |
My website: http://pandu.poluan.info/ |