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

allow-query #173

Closed
geckeon opened this Issue Feb 6, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@geckeon

geckeon commented Feb 6, 2015

Hi,
I think they are a problem with allow-query option.
When they are several subnets in this option, the webui display is correct with ";" but in database they are ","
So named.conf file is in error.
The good syntax is : allow-query {192.168.0.0/24; 192.168.10.0/24;}
But they are : allow-query {192.168.0.0/24, 192.168.10.0/24;}

I can modify the database but i think is beter to correct this.
Perharps see this class address_match_element

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 6, 2015

What version of fmDNS do you see this on?

@WillyXJ WillyXJ added the fmDNS label Feb 6, 2015

@geckeon

This comment has been minimized.

geckeon commented Feb 6, 2015

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 6, 2015

I've been able to reproduce this with fmDNS 1.3.5 and the 2.0 pre-releases. As a workaround until a fix is in place, you can create an ACL with those IPs/subnets and select only that ACL for allow-query.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 9, 2015

fmDNS 1.3.6 has been released with this fix.

@WillyXJ WillyXJ closed this Feb 9, 2015

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