Dustin C. Hatch
d36e0d5a0a
In order to support adding a second DNS server, the BIND zone configuration needs to be partially modularized. While the forwarder definitions for *pyrocufflink.blue*, etc. will remain the same, the *pyrocufflink.red* zone will be different, as it will be a slave zone on the second server. This commit breaks up the definition of the `named_zones` variable into two parts: * `pyrocufflink_red_zones`: This is a list of zone objects for *pyrocufflink.red* and its corresponding reverse zone. On *dns1.pyrocufflink.blue*, these are master zones. On the new server, these will be slaves. * `pyrocufflink_common_zones`: This is a list of zone objects for the zones that are the same on both servers, since they are all forwarding zones. Similarly, the `named_keys` variable only needs to be defined on the master, since DHCP will only send updates there.
50 lines
946 B
YAML
50 lines
946 B
YAML
named_listen:
|
|
- addresses:
|
|
- any
|
|
named_listen_v6:
|
|
- addresses:
|
|
- any
|
|
named_allow_query:
|
|
- any
|
|
named_dnssec_validation: false
|
|
|
|
pyrocufflink_common_zones:
|
|
- zone: pyrocufflink.blue
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.30.0.10
|
|
- 172.30.0.9
|
|
- zone: 0.30.172.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.30.0.10
|
|
- 172.30.0.9
|
|
- zone: pyrocufflink.jazz
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.31.0.4
|
|
- 172.31.0.10
|
|
- zone: 0.31.172.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.31.0.4
|
|
- 172.31.0.10
|
|
- zone: 0.0.0.e.c.3.0.0.0.6.5.0.6.2.ip6.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- fd99:8cd7:6528:fe1e::10:1
|
|
- fd99:8cd7:6528:fe1e::9:1
|
|
- zone: 8.2.5.6.7.d.c.8.9.9.d.f.ip6.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- fd99:8cd7:6528:fe1e::10:1
|
|
- fd99:8cd7:6528:fe1e::9:1
|
|
|
|
named_zones: '{{ pyrocufflink_red_zones + pyrocufflink_common_zones }}'
|