92018-10-21 16:58:23ClintonEbadimention puppet class, no need to mention changes made in squeeze nowadays82015-04-15 06:37:32ClintonEbadiwheezy uses rdnc to restart bind. dust off a bit.72013-01-06 21:35:59ClintonEbadiupdate a bit62012-04-23 04:18:30ClintonEbadi52008-07-07 04:27:53localhostconverted to 1.6 markup42007-12-07 14:36:31MichaelOlsonPoint to Tinydns for adding hcoop subdomains32007-10-22 14:17:08MichaelOlsonAdd item for new hcoop subdomains22007-01-06 16:36:07AdamChlipalaExtraneous "Admin" at the end was getting on my nerves.12006-12-09 23:49:45AdamChlipalaBasic setup of bind is handled by Puppet class hcoop::service::bind9

When adding a new nameserver to hcoop.net, or changing the values of ns[12].hcoop.net update the glue records at our registrar. Otherwise, hcoop.net may stop resolving.

We're using the stock Debian bind9 configuration. You'll need to open the domain input port, and allow outpit port 953 on localhost for rdnc to be able to control bind.

BIND data lives in /etc/bind. This directory is seeded with the default files from the Debian bind9 package. Additionally, we add a zones subdirectory. DomTool periodically deposits /etc/bind/named.conf.local, listing all of our hosted DNS zones and their master/slave statuses and configuration. DomTool also populates /etc/bind/zones with zonefiles referenced by /etc/bind/named.conf.local on any master servers.

/etc/bind/zones must be owned by user bind so that it can modify/create slave zone files. CategorySystemAdministration