ARO does not support more than 1 search domain cluster-wide #4485
Description
Current implementation of /usr/local/bin/aro-dnsmasq-pre.sh and /etc/systemd/system/dnsmasq.service are configured such that we will always only select the first search entry injected into a node via it's local NetworkManager configuration or upstream, which is assumed to be the clustername.domain address. If a customer sets this value explicitly via a static node network file, this clustername.domain entry is overwritten by the first custom domain. As a result, we will not use the cluster domain we'll use the first (only the first) entry they selected.
A problem with this that occurs to me is that we are assuming the cluster name will get injected because by default the interfaces are auto-provisioned and this value is loaded by the upstream DNS options automatically.
If we are setting an interface up manually we must be sure to always list the cluster name as the first entry. May need to examine a resolv-prepender script to enforce this value.
This problem is solved with: #4484 which defines additional search domains.
Note that this must be coupled with a requirement that if not using ipv4.method=auto the cluster name must be injected as ipv4.dns-searches=${1} (followed by any other term).