Ubuntu
resolvconf package

systemd-resolved configuration does not resolve any hostnames

Bug #1915746 reported by Thomas Schweikle on 2021-02-15

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	resolvconf (Ubuntu)	New	Undecided	Unassigned

Bug Description

systemd-resolved will, unter certain circumstances create local only DNS resolution:

# host google.com
;; connection timed out; no servers could be reached

looking at what is going on behind:

# cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf)
nameserver 127.0.0.1
nameserver 127.0.0.53
search <search1> <search2> <search3> DOMAINS

# systemd-resolve --status
Global
         Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: foreign
Current DNS Server: 127.0.0.1
       DNS Servers: 127.0.0.1
        DNS Domain: DOMAINS <search1> <search2> <search3>

Link 2 (eth0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Domain: DOMAINS

Link 3 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (vmnet1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (vmnet2)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 6 (vmnet8)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

This is a useless configuration: dnsmasq asks systemd-resolvd, systemd-resolvd asks dnsmasq. Without ever going to any of the upstream servers. One of them: systemd-resolvd or dnsmasq shall ask upstream servers. But non of them does.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Feb 15 19:16:05 2021
InstallationDate: Installed on 2014-01-31 (2572 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:e,HDMI-1:e
SourcePackage: systemd
UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago)
dmi.bios.date: 11/10/2011
dmi.bios.release: 2.15
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.15
dmi.board.name: 1497
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq 6200 Pro MT PC
dmi.product.sku: XL504AV
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.systemd.resolved.conf: 2021-02-15T19:09:12.129281

Tags:

Revision history for this message

Thomas Schweikle (tps) wrote on 2021-02-15:

CurrentDmesg.txt Edit (121.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (25.6 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (590 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (822 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (23.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.5 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.6 KiB, text/plain; charset="utf-8")
SystemdDelta.txt Edit (1.3 KiB, text/plain; charset="utf-8")
SystemdFailedUnits.txt Edit (1.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (213.6 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (253.6 KiB, text/plain; charset="utf-8")
modified.conffile..etc.systemd.resolved.conf.txt Edit (698 bytes, text/plain; charset="utf-8")

Revision history for this message

Dan Streetman (ddstreet) wrote on 2021-02-17:

> # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf)

resolvconf has been discouraged for a while; you should remove it, and have resolv.conf symlink to the systemd-resolved stub-resolv.conf file.

Even if you need to keep it, this isn't a systemd bug, it would be a bug in resolvconf (or possibly just a local misconfiguration).

affects:

systemd (Ubuntu) → resolvconf (Ubuntu)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubunturesolvconf package