Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Views are sorted alphabetically, not in file order #70

Open
mattfahrner opened this issue Jan 13, 2017 · 2 comments
Open

Views are sorted alphabetically, not in file order #70

mattfahrner opened this issue Jan 13, 2017 · 2 comments

Comments

@mattfahrner
Copy link

In your example of how to use views you give 'trusted' followed by 'default', however in practice the view names get sorted alphabetically, so 'default' will be output before 'trusted'. Since 'default' has catch all "match-clients" of "any", the 'trusted' won't trigger as first catch all 'default' match will always win out.

Changing the view name to something like 'a_trusted' will make it sort prior and fix the issue.

Note you also put in the same example code a 'zones' section, which I don't believe is allowed - if you use 'views', all zones have to be inside views.

@landrypm
Copy link

landrypm commented Mar 9, 2019

Good catch on the ordering of the views in the resulting named.conf file.
The inclusion of the zone definition outside of the views definitions in the example is fine since this module will place all such zones (defined outside of a view) inside all views.

@mattfahrner
Copy link
Author

Thanks!

anarcat pushed a commit to anarcat/puppet-bind that referenced this issue Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants