Hi,

For reference, also see:
https://community.theforeman.org/t/ignore-duplicate-dns-in-case-of-external-nameservers/8172/4
https://community.theforeman.org/t/rfe-change-dns-duplicate-checking-to-be-an-option/8190

There are many cases to think of when you want to add an host to foreman and not to check if this host is already known in the DNS environment. Currently foreman always checks if a host is known and denies to add or change a hosts if a duplicate is found.

In our specific case the host added is indeed known at our DNS service, which is separately managed. The DNS proxy is not enabled and thus active so this check should not be made. (in this environment Foreman does not manage the DNS and DHCP servers)

Another example could be a different (test)cluster which has it’s own DNS server and dns-proxy but ignores the authoritative DNS servers effectively ignoring DNS entries. So if a host in this cluster resolves any entry the local (foreman managed) DNS server should give different answer from the external authoritative DNS servers. The duplicate checking is done by the Foreman server (and not the proxy, where I think it should be done) and in this case also denies updating.
While this example is more fore test environments we do actually have these kinds of setups.

For starters it would help us quite a lot to have a configuration option to disable the whole DNS duplicate checking and let de DNS proxy (if applicable) decide if the addition can be made. (i.e. nsupdate throwing an error)

The patch suggested in https://community.theforeman.org/t/ignore-duplicate-dns-in-case-of-external-nameservers/8172/4
to not to check if there is no DNS proxy also works for the first example.

Cheers,
Maarten