[hcoop/zz_old/ikiwiki] / DaemonAdmin / Bind.mdwn

\r
[[TableOfContents]]\r
\r
= Filesystem layout =\r
\r
On both deleuze and mire, 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.\r
\r
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`.\r
\r
== Permissions ==\r
\r
`/etc/bind/zones` should be owned by user `bind`, since BIND seems to like creating temporary files there.  I've only yet seen this matter during updating of slave zone information.\r
\r
= Adding new hcoop subdomains =\r
\r
This is '''not''' done by editing anything in {{{/etc/bind}}}.  Instead, see ["DomTool/AdminProcedures"].\r
Commit	Line	Data
ee25310d	1	\r
	2	[[TableOfContents]]\r
	3	\r
	4	= Filesystem layout =\r
	5	\r
	6	On both deleuze and mire, 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.\r
	7	\r
	8	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`.\r
	9	\r
	10	== Permissions ==\r
	11	\r
	12	`/etc/bind/zones` should be owned by user `bind`, since BIND seems to like creating temporary files there. I've only yet seen this matter during updating of slave zone information.\r
	13	\r
	14	= Adding new hcoop subdomains =\r
	15	\r
	16	This is '''not''' done by editing anything in {{{/etc/bind}}}. Instead, see ["DomTool/AdminProcedures"].\r