Hi,
I`m not sure that this problem is related to the Bug #27160.
In this case we have a foreman(GUI) VM and two separate foreman-proxies VM(s)
All the 3 VM(s) do not have the nsa1.*****.intra dns server in their /etc/resolv.conf
The “nsa1.*****.intra” is the DNS used by the two forman-proxies via the dns_nsupdate.yml provider.
Ive checked the nsa1.*****.intra logs and couldnt find anything during the time-frame of the error that might point to an issue on the DNS.
Let me explain - Foreman tries to find the DNS record on the DNS proxy directly (ignoring /etc/resolv.conf), unless query_local_nameservers is set to true. In that case, Foreman uses system resolver.
So check if Foreman can do DNS request (UDP) against the DNS proxy configured.
Yes exactly. It literally performs the DNS lookup UDP query against the SOA.
Check your network, maybe a UDP packet being dropped? Also check the timeout value, Foreman only performs one lookup and by default its kinda short I think 5 seconds (dns_conflict_timeout setting), increase that. In 1.24 it’s now an array where you can specify multiple tries like [5, 5, 10, 30] seconds.