welcome: please sign in

Diff for "DaemonAdmin/Bind"

Differences between revisions 3 and 4
Revision 3 as of 2007-10-22 14:17:08
Size: 838
Editor: MichaelOlson
Comment: Add item for new hcoop subdomains
Revision 4 as of 2007-12-07 14:36:31
Size: 832
Editor: MichaelOlson
Comment: Point to Tinydns for adding hcoop subdomains
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 14: Line 13:
= Adding new hcoop subdomains = = Adding new HCoop subdomains =
Line 16: Line 15:
This is '''not''' done by editing anything in {{{/etc/bind}}}. Instead, see ["DomTool/AdminProcedures"]. This is '''not''' done by editing anything in {{{/etc/bind}}}. Instead, see ["DaemonAdmin/Tinydns"].

TableOfContents

1. Filesystem layout

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.

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.

1.1. Permissions

/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.

2. Adding new HCoop subdomains

This is not done by editing anything in /etc/bind. Instead, see ["DaemonAdmin/Tinydns"].

DaemonAdmin/Bind (last edited 2018-10-21 16:58:23 by ClintonEbadi)