Infoblox DNS provider have a single setting called dns_server which is used for two purposes: - HTTP endpoint which is used to communicate with Infoblox - DNS resover used to do conflict checks by common DNS code It's very common to configure Infoblox in a way that the API node does not provide DNS resolver. Currently it's not possible to do such configuration and a manual hotfix is needed: Nn dns_common.rb (find it on the filesystem) change this line: @server = server || "localhost" to @server = "1.2.3.4" where 1.2.3.4 is IP address of (preferably) authoritative DNS server from the Infoblox cluster, or a caching DNS server.
Created redmine issue https://projects.theforeman.org/issues/27046 from this bug
The solution is more complicated and it needs incompatible changes in the smart proxy core DNS API. Therefore this is a temporary solution to override DNS server to query during DNS add/remove operations.
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27046 has been resolved.
So after discussion with Ewoud I worked on a proper fix - DNS conflict check does not use system resolver but Infoblox REST API now.
https://github.com/theforeman/foreman-packaging/pull/3958 https://github.com/theforeman/foreman-packaging/pull/3959
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172