saltstack-formulas/bind-formula
1
0
Fork 0
mirror of https://github.com/saltstack-formulas/bind-formula.git synced 2025-04-10 23:01:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
bind-formula/pillar-with-views.example

101 lines
5.6 KiB
Text
Raw Permalink Normal View History

ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
# -*- coding: utf-8 -*-
# vim: ft=yaml
---
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
bind:
configured_acls: # We have an internal ACL restricted to our
internal: # private IP range.
- 10.0.0.0/8 # In this case, an ACL for external isn't needed
# as that view will be matched by 'any'.
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
# Notice that there is no 'configured_zones' at this indentation level.
# That is because when you are using views, the bind service forces all zones to be served via a view.
#
# Also note - any other zones defined in any other conf files will either need to be commented out, or
# also served via a view using a file include. If you have other zones being served outside of a view, bind will
# fail to start and give you an error message indicating this. You will likely find these externally-defined zones
# in /etc/named.conf and /etc/named.conf.local
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
configured_views:
external: # A view called 'external' to match anything except the 'internal' ACL.
match_clients:
- any # This will match anything, including the public internet.
configured_zones:
mydomain.com: # Notice that this value matches on both views.
type: master
file: external.mydomain.com.txt # Specify the file to be used, which must match the file
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
recursion: 'yes' # name of the zone below under available_zones.
# This filename also must match the corresponding zone name
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
# without the .txt extension (and be sure to use .txt as the extension).
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
notify: false
dnssec: false
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
internal: # The 'internal' view that is restricted to the 'internal' ACL.
match_clients:
- internal # This will match only our ACL named 'internal'.
configured_zones:
mydomain.com: # Same as above - both views will serve the same zone.
type: master
file: internal.mydomain.com.txt # Different file - matches the internal zone below.
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
# Again, this filename must match the corresponding zone name
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
# without the .txt extension (and be sure to use .txt as the extension).
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
recursion: 'yes'
notify: false
dnssec: false
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
available_zones:
external.mydomain.com: # Beginning of the 'external' zone definition.
file: external.mydomain.com.txt # The file in which to save this zone's record set - matches the file
# specified in the 'external' view.
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
soa: # Declare the SOA RRs for the zone
ns: ns1.external.mydomain.com # Required
contact: hostmaster@mydomain.com # Required
serial: auto # Alternatively, autoupdate serial on each change
class: IN # Optional. Default: IN
refresh: 8600 # Optional. Default: 12h
retry: 900 # Optional. Default: 15m
expiry: 86000 # Optional. Default: 2w
nxdomain: 500 # Optional. Default: 1m
ttl: 8600 # Optional. Not set by default
records: # Records for the zone, grouped by type
A:
portal: 50.60.70.80
gateway: 50.60.70.81
directory: 50.60.70.82
ns1: 50.60.70.83
www: 50.60.70.84
NS:
'@':
- ns1
CNAME:
login: portal.mydomain.com.
dashboard: www.mydomain.com.
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
internal.mydomain.com: # Beginning of the 'internal' zone definition.
file: internal.mydomain.com.txt # The file in which to save this zone's record set - matches the file
# specified in the 'internal' view.
ci(yamllint): add rule `empty-values` & use new `yaml-files` setting * Semi-automated using https://github.com/myii/ssf-formula/pull/27 * Fix errors shown below: ```bash bind-formula$ yamllint -s . ./pillar-with-views.example 1:1 warning missing document start "---" (document-start) 2:89 error line too long (93 > 88 characters) (line-length) 4:89 error line too long (98 > 88 characters) (line-length) 5:51 warning comment not indented like content (comments-indentation) 5:89 error line too long (90 > 88 characters) (line-length) 6:1 error trailing spaces (trailing-spaces) 8:89 error line too long (104 > 88 characters) (line-length) 10:89 error line too long (104 > 88 characters) (line-length) 11:89 error line too long (114 > 88 characters) (line-length) 12:89 error line too long (116 > 88 characters) (line-length) 14:1 error trailing spaces (trailing-spaces) 16:89 error line too long (121 > 88 characters) (line-length) 18:89 error line too long (108 > 88 characters) (line-length) 20:89 error line too long (97 > 88 characters) (line-length) 22:89 error line too long (106 > 88 characters) (line-length) 23:22 warning truthy value should be one of [false, true] (truthy) 23:89 error line too long (97 > 88 characters) (line-length) 24:51 warning comment not indented like content (comments-indentation) 24:89 error line too long (110 > 88 characters) (line-length) 24:110 error trailing spaces (trailing-spaces) 25:89 error line too long (122 > 88 characters) (line-length) 26:19 warning truthy value should be one of [false, true] (truthy) 27:19 warning truthy value should be one of [false, true] (truthy) 29:89 error line too long (113 > 88 characters) (line-length) 31:89 error line too long (98 > 88 characters) (line-length) 33:89 error line too long (104 > 88 characters) (line-length) 35:89 error line too long (101 > 88 characters) (line-length) 36:51 warning comment not indented like content (comments-indentation) 36:89 error line too long (112 > 88 characters) (line-length) 36:112 error trailing spaces (trailing-spaces) 37:89 error line too long (122 > 88 characters) (line-length) 38:22 warning truthy value should be one of [false, true] (truthy) 39:19 warning truthy value should be one of [false, true] (truthy) 40:19 warning truthy value should be one of [false, true] (truthy) 43:89 error line too long (96 > 88 characters) (line-length) 44:89 error line too long (119 > 88 characters) (line-length) 45:51 warning comment not indented like content (comments-indentation) 46:1 error trailing spaces (trailing-spaces) 50:89 error line too long (99 > 88 characters) (line-length) 57:89 error line too long (89 > 88 characters) (line-length) 70:1 error trailing spaces (trailing-spaces) 71:89 error line too long (96 > 88 characters) (line-length) 72:89 error line too long (119 > 88 characters) (line-length) 73:51 warning comment not indented like content (comments-indentation) 74:1 error trailing spaces (trailing-spaces) 78:89 error line too long (99 > 88 characters) (line-length) 85:89 error line too long (89 > 88 characters) (line-length) 87:89 error line too long (110 > 88 characters) (line-length) ```
2019-09-10 05:33:31 +01:00
Squash commits Update named.conf.local.jinja Some reorganization of the format. In the for-loop that handles configured_views: - Add if-block on lines 124-128 to allow specifying a file for your view, rather than defaulting to the name of the specified zone. This allows multiple views to serve the same zone, but use a different file. 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. Small comment update. Add comment about using ACLs and views. Create pillar-with-views.example An example of the bind pillar that defines multiple views for internal and external record sets. This doesn't include the other portion of the pillar the defines the bind config - this is zones, views and ACLs only. The config portion is not affected by this. Add more comment clarification. Add comment explaining file name requirements. The filename must match the corresponding zone name (without the .txt extension) because the config.sls jinja logic uses the filename to match to the zone when setting zone_records. It also is hardcoded to replace ".txt" with "" in order to make this match work, and so .txt extension is required for the logic to work. Update config.sls Add logic to detect a file specified in a view, and match it to a zone under available_zones to enable creating that zone file. Revert back Made a bad commit. Update with the required logic. Added an if-block to test for the file argument in the zone_data, and if found, use that view and update the zone variable to match the zone defined under available_zones. Fix variable set. Set zone based on file with the .txt extension removed. Update README.rst Add paragraph about using views. Update pillar-with-views.example Add some more comments for explanation.
2018-11-14 11:11:07 -05:00
soa: # Declare the SOA RRs for the zone
ns: ns1.mydomain.com # Required
contact: hostmaster@mydomain.com # Required
serial: auto # Alternatively, autoupdate serial on each change
class: IN # Optional. Default: IN
refresh: 8600 # Optional. Default: 12h
retry: 900 # Optional. Default: 15m
expiry: 86000 # Optional. Default: 2w
nxdomain: 500 # Optional. Default: 1m
ttl: 8600 # Optional. Not set by default
records: # Records for the zone, grouped by type
A:
portal: 10.0.0.10 # Here we serve all private IPs as opposed to the public IPs
gateway: 10.0.0.11 # in the external zone.
directory: 10.0.0.12
ns1: 10.0.0.13
www: 10.0.0.14
NS:
'@':
- ns1
CNAME:
login: portal.mydomain.com.
dashboard: www.mydomain.com.
Reference in a new issue Copy permalink