From 4b88c4d7977ca4b140e2b489abe1ad9e7670c804 Mon Sep 17 00:00:00 2001 From: crux-capacitor Date: Wed, 14 Nov 2018 11:17:45 -0500 Subject: [PATCH] Update pillar.example Add documentation and an example on specifying the file to be used for a view, as well as documented that you should not define the top-level 'configured_zones' key when using views. --- pillar.example | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/pillar.example b/pillar.example index a2e29f0..7590294 100644 --- a/pillar.example +++ b/pillar.example @@ -231,7 +231,9 @@ bind: notify: False # Don't notify any NS RRs of any changes to zone also-notify: # Do notify these IP addresses (pointless as - 1.1.1.1 # notify has been set to no) - - 2.2.2.2 + - 2.2.2.2 # If using views, do not define configured_zones + # at this indentation level - define it using the sub-key + # of your configured_view. sub.domain2.com: # Domain zone with DNSSEC type: master # We're the master of this zone @@ -279,7 +281,16 @@ bind: configured_zones: # Zones that our view is applicable to my.zone: # We've defined a new zone in here type: master - notify: False + file: example.com.txt # Optional: specify the zone file to be used for this view. + # otherwise it will default to the file matching the name of the zone that you + # specify here. + # The file name must match what you have entered for 'file' in the zone under + # 'available_zones'. + # This allows you to define multiple views that serve the same zone, but + # serve a different record set. + # If doing this, you need to configure the zones and their record sets + # underneath the 'available_zones' section. + notify: False update_policy: # A given update policy - "grant core_dhcp name dns_entry_allowed_to_update. ANY"