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

Ubuntu server options are written to named.conf #22

Closed
vjorge opened this Issue Oct 8, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@vjorge

vjorge commented Oct 8, 2013

Hi,

I have a server that runs bind version BIND 9.8.1-P1. The problem is that the dns options are written to named.conf instead of named.conf.options, therefore making config files non loadable.

Can you please add an option to write the dns options to the named.conf.options file.

Thanks,

Vitor

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Oct 8, 2013

Hi Vitor,

Thanks for the request. Could I please get a little more information about this? What config files end up being non-loadable with the way fmDNS writes named.conf? I'm trying to reproduce this case. Would this issue be appropriately resolved if you set the server "Config File" value to /etc/bind/named.conf.options?

Thanks.

@vjorge

This comment has been minimized.

vjorge commented Oct 8, 2013

Hi,

Many thnks for your reply.

If you use red hat or based then the option tag can be inside named.conf
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Reference_Guide/s1-bind-namedconf.html

In the case of ubuntu, the options are defined on a specific
file(named.conf.options), separated from the zones definition file
named.conf.

https://help.ubuntu.com/community/BIND9ServerHowto

In the case of the facileManager it only needs to write the options to a
different file,named named.conf.options, according to bind documentation.

More exactly if i use your software i can set everything to work except the
options because those get written into named.conf, if i remove those
entries and copy to named.conf.options then it works fine.

hope this helps, please call me if more info is needed.

Many thanks for your help.

Regards,

Vitor

2013/10/8 WillyXJ notifications@github.com

Hi Vitor,

Thanks for the request. Could I please get a little more information about
this? What config files end up being non-loadable with the way fmDNS writes
named.conf? I'm trying to reproduce this case. Would this issue be
appropriately resolved if you set the server "Config File" value to
/etc/bind/named.conf.options?

Thanks.


Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-25891619
.

WillyXJ pushed a commit that referenced this issue Oct 8, 2013

WillyXJ WillyXJ
Issue #22
Added support for Ubuntu systems to save named options in
named.conf.options.
@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Oct 8, 2013

This is resolved in 1.0-rc4. Watch for an in-app update notification.

@WillyXJ WillyXJ closed this Oct 8, 2013

@vjorge

This comment has been minimized.

vjorge commented Oct 8, 2013

Great.

Many thanks for your help.

Regards,

Vitor

2013/10/8 WillyXJ notifications@github.com

This is resolved in 1.0-rc4. Watch for an in-app update notification.


Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-25925915
.

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