Bug #12774
closedDNS nsupdate configuration woes
Description
According to the examples [1] [2] as well as the puppet-foreman_proxy module [3], the configuration (dns_key, dns_server) for the nsupdate DNS provider is expected to be put in the settings.d/dns_nsupdate.yml file. Unfortunately, with the version I'm testing on (foreman-proxy 1.9.1 on FreeBSD) the configuration in this file is ignored and I have to put the configuration for nsupdate in the settings.d/dns.yml file instead.
Result with configuration in settings.d/dns_nsupdate.yml:
D, [2015-12-11T01:21:22.198596 #2465] DEBUG -- : running /usr/local/bin/nsupdate D, [2015-12-11T01:21:22.200416 #2465] DEBUG -- : nsupdate: executed - server localhost
=> parameters dns_key and dns_server ignored
Result with configuration in settings.d/dns.yml:
D, [2015-12-11T01:26:18.687920 #2521] DEBUG -- : running /usr/local/bin/nsupdate -k /usr/local/etc/namedb/rndc.key D, [2015-12-11T01:26:18.689874 #2521] DEBUG -- : nsupdate: executed - server dns-server.example.com
=> parameters dns_key and dns_server accepted
Is this already fixed for 1.10 or is this just a documentation issue?
Sorry I don't have access to the newest version ATM.
[1] https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example
[2] https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns_nsupdate.yml.example
[3] https://github.com/theforeman/puppet-foreman_proxy/blob/master/templates/dns_nsupdate.yml.erb#L6-L8