Hi Jeffrey,

That's true but right now I have no control over OpenShift/OKD behavior.

I even managed to make my DNS stop sending 'domain-search' (clearly visible in the NM connection) but NM still applies the domain as such.

On top of that I can't find dhcp-client in the repo ,which could be a possible solution to replace NM built-in DHCP client.

Best Regards,
Strahil Nikolov



On Sun, Jan 28, 2024 at 0:14, Jeffrey Walton
<noloader@gmail.com> wrote:
On Sat, Jan 27, 2024 at 9:19 AM Strahil Nikolov via users
<users@lists.fedoraproject.org> wrote:
>
> Hi all,
>
> I am looking for some help to adjust systemd-resolved to still use DHCP (ip, gateway and dns servers) but to avoid using the dns search provided over DHCP.
>
> The reason behind is that OKD4's coredns (Fedora CoreOS) appends the search stanza (first entry) that is taken from the host and then sends it to the upstream server.
> Ex:
> /etc/resolv.conf contains:
> search my.domain my.other.domain
>
> CoreDNS query becomes 'quay.io.my.domain' instead of 'quay.io'.

Related, whomever is specifying quay.io needs to specify 'quay.io.',
with the trailing dot. The trailing dot signifies a Fully Qualified
Domain Name (FQDN). The trailing dot means the dns name starts at the
top of the DNS tree, and search domains won't (should not?) be added.
Or maybe I should say, won't be added in a proper functioning
implementation.

Jeff