How do hosting companies do realtime changes?

[Simon Waters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Vande More wrote:
>
> And while perl is writing my named.conf or even a dns file, even if
> everything is loaded into memory, will it affect the running named
process?
> (I.E. It takes a good 2 minutes to generate everything on a full rewrite.
> Though if I did go this route, timestamps would affect which zone would be
> regenerated.)

If you have 3 name servers stopping and starting one to update master
copies isn't a big issue, it would only affect changes to the conf file
anyway. If it worries you, use a hidden master.

> Sure there are tons of ways to do that, but which way to people feel most
> comfortable with?

I've seen all 3 ways done in various places (e.g. database interface,
recreating zone files, and nsupdate, they all work fine).

I feel most comfortable with zonefiles on disk, where they can be
checked (named-check*), and will exist even if the database is down, but
I think these days nsupdate offers some good sanity checking.

Also with the zone files on disk named behaves like named, where as I've
seen some database implementations with "funny bugs", better the devil
you know in some instances.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/ns99GFXfHI9FVgYRAj1JAJ9kRyXLl4HUXiwxBWLZ8RcSF7K+VACfRGUI
9raYTVW1XODjhka5T9O/7Xw=
=p+pU
-----END PGP SIGNATURE-----