unkinben/puppet-bind
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document the relationship between zones and views

Browse Source 
Clarify that a zone must be included in a view and may be included in multiple
views in order to be declared in the nameserver's configuration.
This commit is contained in:
Nate Riffe 2015-01-19 11:13:58 -06:00
parent e13e18ad82
commit 63450a9e21
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -100,10 +100,12 @@ the `bind::acl` declaration.
###bind::zone ###bind::zone
Declares a zone in the server's configuration. The corresponding zone file will Declares a zone. Each zone must be included in at least one view in order to be
be created if it is absent, but any existing file will not be overwritten. Only included in the server's configuration, and may be included in multiple views.
the `zone_type` is required. If `domain` is unspecified, the title of the The corresponding zone file will be created if it is absent, but any existing
`bind::zone` declaration will be used as the domain. file will not be overwritten. Only the `zone_type` is required. If `domain` is
unspecified, the title of the `bind::zone` declaration will be used as the
domain.
A master zone with DNSSec disabled which allows updates using a TSIG key and A master zone with DNSSec disabled which allows updates using a TSIG key and
zone transfers to servers matching an acl: zone transfers to servers matching an acl:
@ -158,8 +160,9 @@ A forward zone:
###bind::view ###bind::view
Declares a view in the BIND configuration. There must be at least one view Declares a view in the BIND configuration. In order to declare zones in a
declaration. server configuration there must be at least one view declaration which includes
the zones.
A common use for views is to use a single dual-homed nameserver as a resolver A common use for views is to use a single dual-homed nameserver as a resolver
on a private network and an authoritative non-resolving nameserver on the on a private network and an authoritative non-resolving nameserver on the