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

missing recursion option in views #46

Closed
carock96 opened this Issue Dec 9, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@carock96

carock96 commented Dec 9, 2013

With Bind, you can also set recursion yes/no in the views.

view "external" {
match-clients { any; };
recursion no;

The "recursion" option does not appear in the list inside the view configuration

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Dec 9, 2013

If you remove it from the global options then it will become available for use in all views. It was designed that way as I came across some options that can either go in views config or the global config, but not both. So, it was easier to make them all with either/or support rather than and/or.

Would it make more sense to find a solution to support options in views and/or global configs?

@carock96

This comment has been minimized.

carock96 commented Dec 9, 2013

I’m not sure if there’s a better or worse way. Options that overlap different areas of the configuration can be frustrating for both of us ;-)

I’m migrating a DNS server to a new one. It has over 800 DNS zones on it, and it’s working !! ☺

I’m just trying to make sure there aren’t too many changes from my working named.conf to the one I end up with using your software.

The one I have is old and been through a lot of Bind upgrades, so some of the options and settings may not really be necessary anymore the way I happen to have it configured.

I appreciate the help.

Thanks,
Chuck

From: WillyXJ [mailto:notifications@github.com]
Sent: Monday, December 09, 2013 3:48 PM
To: WillyXJ/facileManager
Cc: Chuck Rock
Subject: Re: [facileManager] missing recursion option in views (#46)

If you remove it from the global options then it will become available for use in all views. It was designed that way as I came across some options that can either go in views config or the global config, but not both. So, it was easier to make them all with either/or support rather than and/or.

Would it make more sense to find a solution to support options in views and/or global configs?


Reply to this email directly or view it on GitHubhttps://github.com//issues/46#issuecomment-30177047.

WillyXJ pushed a commit that referenced this issue Dec 27, 2013

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Dec 27, 2013

Changes have been checked in to the 1.1-release branch (https://github.com/WillyXJ/facileManager/tree/1.1-release) that support the use of config options in global AND views configurations. Feel free to test the changes out if you have a test or POC environment.

Please note, v1.1 is not released so it cannot be considered stable yet.

@WillyXJ WillyXJ closed this Dec 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment