Bug#947688: systemd-networkd: Python socket.getfqdn() not working properly when resolv.conf lacks "domain" key

[Michael Biebl]

Control: tags -1 + moreinfo

Am 29.12.19 um 11:41 schrieb Dirk Heinrichs:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: normal
> Tags: upstream
> 
> Hi,
> 
> first, a short description of the overall setup: A private (aka home) network
> using Samba AD with ISC DHCP for network management and setup. All machines run
> up-to-date Debian 10 (buster). I mainly run two types of machines (reg. their
> network setup mechanism): Laptops, which use Network-Manager + systemd-
> resolved, and others, which use systemd-networkd + systemd-resolved (or better:
> should use). I also use Salt for overall systems management.
> 
> The problem with the latter setup is that it breaks Python's socket.getfqdn()
> function when
> 
>         1) systemd-resolved is running
>         2) /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-
> resolv.conf
>         3) /etc/resolv.conf lacks a "domain" entry
> 

not quite sure what you mean by "domain" entry.

Can you post a (full copy of a) working/non-working /etc/resolv.conf?

Is Python reading /etc/resolv.conf directly or does it use NSS?
Is libnss-resolve installed (and enabled)?


-------------- 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/20191229/bed2e020/attachment.sig>