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

Wrong cfgEntryFormat written to Bind config file (address_match_element) #237

Closed
dialsc opened this issue Aug 11, 2015 · 3 comments
Closed

Wrong cfgEntryFormat written to Bind config file (address_match_element) #237

dialsc opened this issue Aug 11, 2015 · 3 comments

Comments

@dialsc
Copy link

@dialsc dialsc commented Aug 11, 2015

Hi,

I've got no glue if I'm just missing the know how but I just started to work with fmDNS (using the latest version available today) and ran into a problem. I tried to configure a list of allowed networks in the "options" dialog, the config name is e.g. allow-query.

As soon as I add more than one value to the option parameter, the configuration file created becomes invalid.

Example: Add two networks as the option value like this: 10.0.10.0/24 10.0.20.0/24
This becomes the following value in the options configuration file @ the server: allow-query { 10.0.10.0/24,10.0.20.0/24; };

You can add a couple more networks, they will all get seperated using commas instead of semicolons except after the last entry, there a semicolon gets included. It looks like this happens with all the option parameters which are of type address_match_element.

So, if I'm really just missing the knowledge how to do it, it would be cool if someone could tell me, plz. Otherwise I feel this could be bug.

Greez,

Dirk

@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Aug 11, 2015

Hi Dirk,

I have confirmed this is a bug. Until this is fixed, you can create an ACL with your entries and then add the ACL to the allow-query option as a workaround.

@dialsc
Copy link
Author

@dialsc dialsc commented Aug 11, 2015

Hi,

Thanks a lot for your very fast answer and the workaround!

Greez,

Dirk

@WillyXJ WillyXJ added this to the 2.x release milestone Sep 3, 2015
@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Nov 16, 2015

Code submitted and will be released with the next build.

@WillyXJ WillyXJ closed this Nov 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants