Bug 1392355

Hello Dominic


Can you search the page at the link in comment 0 and confirm if any other occurrences of the word "nsupdate" on that page should be changed in addition to the option in the  "/etc/foreman-proxy/settings.d/dns.yml" file example that comment 0 asks to be changed.

Thank you

Assigning to Charles for review.

Here is a snippet from my freshly installed Satellite 6.2. Does it help you to identify what the change was?

[root@amd-ma78gm-01 ~]# find /etc/foreman-proxy/settings.d
/etc/foreman-proxy/settings.d
/etc/foreman-proxy/settings.d/bmc.yml
/etc/foreman-proxy/settings.d/dhcp.yml
/etc/foreman-proxy/settings.d/dhcp_isc.yml
/etc/foreman-proxy/settings.d/dhcp_ms_native.yml
/etc/foreman-proxy/settings.d/dhcp_virsh.yml
/etc/foreman-proxy/settings.d/dns.yml
/etc/foreman-proxy/settings.d/dns_dnscmd.yml
/etc/foreman-proxy/settings.d/dns_nsupdate.yml
/etc/foreman-proxy/settings.d/dns_nsupdate_gss.yml
/etc/foreman-proxy/settings.d/dns_virsh.yml
/etc/foreman-proxy/settings.d/facts.yml
/etc/foreman-proxy/settings.d/logs.yml
/etc/foreman-proxy/settings.d/puppet.yml
/etc/foreman-proxy/settings.d/puppetca.yml
/etc/foreman-proxy/settings.d/realm.yml
/etc/foreman-proxy/settings.d/templates.yml
/etc/foreman-proxy/settings.d/tftp.yml
/etc/foreman-proxy/settings.d/openscap.yml
/etc/foreman-proxy/settings.d/discovery.yml
/etc/foreman-proxy/settings.d/pulp.yml
/etc/foreman-proxy/settings.d/pulpnode.yml
/etc/foreman-proxy/settings.d/dynflow.yml
/etc/foreman-proxy/settings.d/remote_execution_ssh.yml
[root@amd-ma78gm-01 ~]# cat /etc/foreman-proxy/settings.d/dns.yml
---
# DNS management
:enabled: https
# valid providers:
#   dns_dnscmd (Microsoft Windows native implementation)
#   dns_nsupdate
#   dns_nsupdate_gss (for GSS-TSIG support)
#   dns_virsh (simple implementation for libvirt)
:use_provider: dns_nsupdate
# use this setting if you want to override default TTL setting (86400)
:dns_ttl: 86400

Hello Charles

The way I see it, `nsupdate` is still the correct name for the utility supplied by bind-utils.

So all example *commands* sre still correct.

The only question is then the from step 5.

Run the satellite-installer script to make the following persistent changes to the /etc/foreman-proxy/settings.d/dns.yml file. 

--foreman-proxy-dns-provider=nsupdate

Re comment 4

If you look in /etc/foreman-proxy/settings.d/dns_nsupdate.yml you will see:

---
#
# Configuration file for 'nsupdate' dns provider
#

:dns_key: /etc/rndc.key
# use this setting if you are managing a dns server which is not localhost though this proxy
:dns_server: 10.xx.xx.xxx


So that seems to suggest the option "--foreman-proxy-dns-provider=nsupdate" should be changed to "--foreman-proxy-dns-provider=dns_nsupdate" 

Would be nice to get confirmation.

Hi Stephen,

I think it can still be nsupdate, according to the output of # satellite-installer --help:

On Capsule 6.2.7:
# satellite-installer --help | grep dns
~~~
--dns-provider                DNS provider (default: "nsupdate")
~~~

On Satellite 6.2.7:
# satellite-installer --help | grep dns
~~~
--foreman-proxy-dns-provider  DNS provider (default: "nsupdate")
~~~

OK, thanks Kenny

Lets close this as NOTABUG, anyone can reopen it if they have a reason why we need to mention this low level change (as shown in comment 3, :use_provider: dns_nsupdate).


Thank you

Seems you cannot rely on installer script's "--help" usage statement because  it seems the installer script accepts any value and then tells you that is the default:

~]# satellite-installer --help | grep dns
--foreman-proxy-dns-provider  DNS provider (default: "Fort_Knox") 

I will raise a bug.

Re comment 8

Bug 1441285 - Installer script's "--help" output use of "default" is misleading

Clearing old needinfo request.