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

[Michael Biebl]

Am 29.12.19 um 14:12 schrieb Dirk Heinrichs:
> Michael Biebl:
> 
>> not quite sure what you mean by "domain" entry.
> 
>     "domain example.com"
> 
>> Can you post a (full copy of a) working/non-working /etc/resolv.conf?
> 
> Working:
> 
>     nameserver <real IP address of nameserver>
>     search <domain>
>     domain <domain>
> 
> Non-Working (as created automatically by systemd-resolved):
> 
>     nameserver 127.0.0.53
>     options edns0
>     search <domain>


Are you aware of the "UseDomain=" option (see man systemd.network)?
Does it help if you set that option?

If not, we probably need a dump of the DHCP requests and a verbose debug
log of systemd-networkd.

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