Bug#947688: systemd-networkd: Python socket.getfqdn() not working properly when resolv.conf lacks "domain" key
Michael Biebl
biebl at debian.org
Sat Feb 1 06:28:08 GMT 2020
On Tue, 31 Dec 2019 08:41:04 +0100 Dirk Heinrichs
<dirk.heinrichs at altum.de> wrote:
> Michael Biebl:
>
> > I've uploaded v244 to buster-backports so you should be able to test if
> > you can still reproduce the problem there.
>
> Great, thanks a lot, will do. I've also meanwhile tested this in an Arch
> Linux Container and it shows the same behaviour. However, it seems I was
> somehow wrong reg. the need for the "domain" keyword in resolv.conf. The
> "search" keyword seems to be enough, but this is missing unless I add a
> proper "Domains=..." line to resolved.conf and restart it, although it
> should get the domain from the DHCP server.
>
Did you find time to reproduce the issue with v244?
Btw, if you run
host $hostname
or
resolvectl query $hostname
does it work for you? It seems to work for me at least using 244.1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200201/c2425c91/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list