Re: BIND
From: Bennett Todd (bet@rahul.net)Date: 10/19/01
- Previous message: focus-sun@anastrophe.com: "BIND"
- In reply to: focus-sun@anastrophe.com: "BIND"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 18 Oct 2001 23:28:19 -0400 From: Bennett Todd <bet@rahul.net> To: focus-sun@anastrophe.com Subject: Re: BIND Message-ID: <20011018232819.B19071@rahul.net>
2001-10-18-18:13:01 focus-sun@anastrophe.com:
> Sort of in this vein, is anyone here using djbdns in a large ISP
> environment?
Haven't worked at a large ISP environment, but I've used djbdns in
several settings, very happily.
> I'd like to switch over to it, since I'm sick to death of BIND
> and it's continued bugginess/insecurity, but we host a couple of thousand
> customer domains, and I've not been able to find a real 'cookbook' for
> converting 'en masse'...
Conversion is [relatively] easy, for the most part; you set up new
nameservers, initially running data files produced by using axfr-get
to pull via AXFR from your BIND nameservers. Then you get people to
start testing the new nameservers. Once you're satisfied that the
data they're serving is cool, you shift the delegations and you're
done. Then you can start cleaning up the data.
The one thing that might involve more work is if you're doing huge
numbers of zones slaved off customer nameservers via on-demand
pushes; the notify stuff isn't implemented in djbdns, although other
folks have hacked it up in scripts built around djbdns.
The best is if you can ditch bind altogether, maintain all zone data
in tinydns-data format, replicating with rsync over ssh.
-Bennett
- application/pgp-signature attachment: stored
- Previous message: focus-sun@anastrophe.com: "BIND"
- In reply to: focus-sun@anastrophe.com: "BIND"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
