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: warning in configuration when I preview config #385

Closed
5 tasks done
beza2000 opened this issue Aug 2, 2017 · 2 comments
Closed
5 tasks done

[BUG] fmDNS: warning in configuration when I preview config #385

beza2000 opened this issue Aug 2, 2017 · 2 comments

Comments

@beza2000
Copy link

beza2000 commented Aug 2, 2017

Replace everything between stars with current version of your facileManager and module installations:
fM Version : 3.0.1
fmDNS Version : 3.0.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.

When I use Keys, I expect Key Name don't change.
But when I previewed config, I had error after named-checkconf - Key Name ended with a dot:

Your named configuration contains one or more errors:
/etc/named.conf:94: unknown key 'rndc-key'
---
====== /etc/named/zones/views.conf.internal.keys:
1 // This file was built using fmDNS 3.0.1 on Wed, 02 Aug 2017 16:04:28 +0300 Europe/Moscow
2 
3 key "rndc-key." {
4 	algorithm hmac-md5;
5 	secret "U0gwg+QNPnM6IlS/jCWLXw==";
6 };
======

====== /etc/named.conf:
 93 controls {
 94 	inet * allow { localhost; } keys { "rndc-key"; };
 95 };
======

@beza2000 beza2000 changed the title [BUG] fmDNS: error when I preview config [BUG] fmDNS: warning in configuration when I preview config Aug 2, 2017
@WillyXJ
Copy link
Owner

WillyXJ commented Aug 2, 2017

Confirmed this behavior only exists when a key is associated with a view.

@WillyXJ
Copy link
Owner

WillyXJ commented Aug 8, 2017

This is now fixed in 3.0.3 and later.

@WillyXJ WillyXJ closed this as completed Aug 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants