b3ffa2b5f3
If the hostname of a system is set to an fqdn, glibc traditionally derives a search domain from it if none is explicitly configured. This is a bit weird, and we currently don't do that in our own search path logic. Following #17193 let's turn this behaviour off for now. Yes, this has a slight chance of pissing people off who think this behaviour is good. If this is indeed an issue, we can revisit the issue but in that case if we readd the concept we should do it properly: derive the search domain from the fqdn in our codebase too and report it in resolvectl, and in our generated stub files. But I have the suspicion most people who set the hostname to an fqdn aren#t even aware of this behaviour nor want it, so let's wait until people complain. Fixes: #17193
20 lines
710 B
Plaintext
20 lines
710 B
Plaintext
# This file belongs to man:systemd-resolved(8). Do not edit.
|
|
#
|
|
# This is a static resolv.conf file for connecting local clients to the
|
|
# internal DNS stub resolver of systemd-resolved. This file lists no search
|
|
# domains.
|
|
#
|
|
# Run "resolvectl status" to see details about the uplink DNS servers
|
|
# currently in use.
|
|
#
|
|
# Third party programs must 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 .
|