saltstack-formulas/bind-formula
1
0
Fork 0
mirror of https://github.com/saltstack-formulas/bind-formula.git synced 2025-04-16 09:40:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update pillar.example

Browse source 
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.
This commit is contained in:
crux-capacitor 2018-11-14 11:17:45 -05:00 • committed by GitHub
parent d387599e77
commit 4b88c4d797
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
pillar.example
View file

@ -231,7 +231,9 @@ bind:
notify: False # Don't notify any NS RRs of any changes to zone notify: False # Don't notify any NS RRs of any changes to zone
also-notify: # Do notify these IP addresses (pointless as also-notify: # Do notify these IP addresses (pointless as
- 1.1.1.1 # notify has been set to no) - 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 sub.domain2.com: # Domain zone with DNSSEC
type: master # We're the master of this zone type: master # We're the master of this zone
@ -279,7 +281,16 @@ bind:
configured_zones: # Zones that our view is applicable to configured_zones: # Zones that our view is applicable to
my.zone: # We've defined a new zone in here my.zone: # We've defined a new zone in here
type: master 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 update_policy: # A given update policy
- "grant core_dhcp name dns_entry_allowed_to_update. ANY" - "grant core_dhcp name dns_entry_allowed_to_update. ANY"