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

Feature: server clause #218

Closed
NickNickNickNick opened this Issue May 28, 2015 · 10 comments

Comments

Projects
None yet
3 participants
@NickNickNickNick
Copy link

commented May 28, 2015

I am using fmDNS 2.0.1 and trying add a server clause (for TSIG) but not able to find it. I was able to add the key and allow-transfer option but not seeing the server clause.

key "tsig-key" {
algorithm hmac-md5;
secret " contents\of\secret\key";
};

allow-transfer { key tsig-key; };

Should look something like this:

server 192.168.1.100 {
keys { tsig-key; };
};
server 192.168.1.101 {
keys { tsig-key; };
};
server 192.168.1.102 {
keys { tsig-key; };
};

Could this be added to fmDNS?

Information on server clause: http://www.zytrax.com/books/dns/ch7/server.html
Information on TSIG: ftp://ftp.isc.org/isc/bind/cur/9.9/doc/arm/Bv9ARM.ch04.html#tsig

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented May 28, 2015

Hi Nick,

The server clause isn't fully supported (yet), but you should be able to use the key feature. Once you define the key, go to Config->Servers, click the edit button for the server you want, and in the box you can select the key. Let me know if this doesn't achieve what you're looking for.

@NickNickNickNick

This comment has been minimized.

Copy link
Author

commented May 28, 2015

Hey thank you for your reply. I have the keys feature working and it should get be by for now. Just wondering when server clauses will be fully supported in fmDNS?

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented May 29, 2015

Good question and unfortunately there isn't a target date let alone target version yet. Still lots to do. I'll leave this issue open to track the feature.

@WillyXJ WillyXJ added this to the 3.0 release milestone Dec 2, 2015

@andrewhotlab

This comment has been minimized.

Copy link

commented Jan 20, 2018

It would be great to have this feature. We need to make fmDNS's managed servers transfer a zone from other's name server using TSIG, and we are still unable to do it. We are running fmDNS 3.1.2. Thanks!

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented Jan 16, 2019

I've been stuck on this feature for quite some time because of the design and intention of the Config->Servers page. That was intended to configure the fmDNS servers so the clause has very limited support. To change that, it might be best to remove the key select from the server and create a new page for "remote" servers where the full servers clause would be supported. Would that make sense or be the best approach to implement this feature?

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented Jan 16, 2019

Another idea is to support fmDNS servers and remote servers all within the same page. The configuration window would just be different based on a drop-down selection for "local" and "remote" servers.

The configuration window would, of course, include the supported server clause options. This might be a better way to go for ease-of-use.

@andrewhotlab

This comment has been minimized.

Copy link

commented Jan 17, 2019

From a logic perspective, since the BIND server configuration statement can contains host-specific data (i.e. the query-source option), it would be better to include it in the Config -> Servers page, even if I guess that a dedicated page for "remote servers" would be easier to use.

I vote for the "easier-to-develop" way! :)

@WillyXJ WillyXJ referenced this issue Mar 15, 2019

Open

[FEATURE REQUEST] Add option 'server' #434

5 of 5 tasks complete

@WillyXJ WillyXJ added the In progress label Mar 15, 2019

@WillyXJ WillyXJ removed this from the 3.0 release milestone Mar 16, 2019

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented Mar 17, 2019

This is now implemented in fmDNS 3.3 and later.

@WillyXJ WillyXJ closed this Mar 17, 2019

@andrewhotlab

This comment has been minimized.

Copy link

commented Mar 18, 2019

Wonderful! Thank you so much for this work: we upgraded to the latest release, defined a few "remote" servers and set for them TSIG keys... zone transfers from those server to the ones managed with fmDNS are now authenticated!

Just a question about the the count of remote servers that we noticed in the left menu, as if there where some change to commit (see attached screenshot): it's a normal behavior, or we misconfigured something?

Screenshot_2019-03-18_11-36-16

WillyXJ pushed a commit that referenced this issue Mar 18, 2019

@WillyXJ

This comment has been minimized.

Copy link
Owner

commented Mar 18, 2019

Thanks for the report @andrewhotlab - the menu badge counts issue you are experiencing is found to be a bug that was introduced with this feature. It will be fixed in fmDNS v3.3.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.