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

[BUG] fmDNS Editor works differently in Global Options and view Options #429

4 tasks done
beza2000 opened this issue Jan 14, 2019 · 1 comment
4 tasks done


Copy link
Task lists! Give feedback

@beza2000 beza2000 commented Jan 14, 2019

fM Version : 3.1.1
{fmDNS} Version : 3.1.2

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
  • [] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

(BUG | ISSUE) Expected Behavior:
When I add options, I expexted the same editor to work in Global Options and view Options.

(BUG | ISSUE) Actual Behavior:
The editor in Global Options and view Options has different rules.

(BUG | ISSUE) Steps to reproduce:
In Global Options I can add:
allow-update key "dnsupdater";
When view Options I get only:
allow-update key;

Also in view Options I can not do
view "internal" {
match-clients { !key external; 10.0.1/24; };
I receive only
view "internal" {
match-clients { !key; 10.0.1/24; };

Copy link

@WillyXJ WillyXJ commented Mar 17, 2019

This is now fixed in fmDNS 3.3 and later.

@WillyXJ WillyXJ closed this Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants