Moin,
da mich die Sache auch interessiert hat, habe ich das mal nachgebaut. Erst konnte ich das Verhalten von MSfree nachvollziehen.
Dann bin ich aber auf einen
issue von systemd gestoßen, der das gleiche Verhalten zeigte. Bei dem war es allerdings ein Problem von seinem System.
Ich habe dann allerdings mal seine .network probiert. Und siehe da, die Suchdomain kommt an.
Meine .network sieht jetzt so aus:
Code: Alles auswählen
[root@test~]# cat /etc/systemd/network/enp1s0.network
[Match]
Name=enp1s0
[Network]
DHCP=true
[DHCP]
UseDomains=true
Die resolfv.conf sieht jetzt so aus:
Code: Alles auswählen
[root@test ~]# ll /etc/res*
lrwxrwxrwx 1 root root 39 21. Jul 09:42 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
[root@test ~]# cat ../run/systemd/resolve/stub-resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search meine-domain.com
Die "echte" resolv.conf so:
Code: Alles auswählen
[root@test ~]# cat ../run/systemd/resolve/resolv.conf
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 192.168.1.225
nameserver 192.168.1.230
search meine-domain.com
Also muss man mehr angeben in der .network als vorher.
Aber das sollte der Paketmanager bzw. die Pakete doch selbst hinfummeln können, oder?
