pc wont resolve any names until /etc/resolv.conf is edited by hand

[Thomas Schweikle]

In /etc/systemd/resolved.conf I've entered the nameserver to use:
[Resolve]
DNS=172.18.8.1
#FallbackDNS=
Domains=fritz.box
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes

In /etc/resolv.conf after rebooting:
nameserver 127.0.0.53
options edns0
search fritz.box

No names from anywhere are solved. This systemd-resolver just does nothing. It does not even forward any request to 172.18.8.1!

As soon as I edit /etc/resolv.conf, replacing 127.0.0.53 with 172.18.8.1 it starts to work as it is expected to. Looks like systemd-resolved is broken by design.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: systemd 242-7ubuntu3.2
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 27 19:16:22 2019
InstallationDate: Installed on 2019-09-09 (79 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-23-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603

[Dan Streetman (ddstreet)]

> Looks like systemd-resolved is broken by design.

er, no.

Without editing resolv.conf, what do these commands show:

$ systemctl --no-pager status systemd-resolved

$ resolvectl --no-pager

$ resolvectl query google.com

[Launchpad Janitor (janitor)]

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]