[Bug 1812637] [NEW] systemd-resolved stops resolving

Wolf Rogner war at rsb.at
Mon Jan 21 11:10:59 UTC 2019 

Public bug reported:

Regularly (= after about 15 mins of use) the systemd-resolved service
stops resolving DNS names (any).

Configuration:
Two domains defined - one internal, one for external services
DNS server does not provide DNSSEC services
Both domains are in the search path (served by DHCP)

Effect:
Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins.

Workaround:
from the client CLI
sudo systemctl restart systemd-resolved.service

Background:
A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC.

I found discussions about "the correct way" DNS works (with only one
domain).

Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked
fine).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: systemd 239-7ubuntu10.6
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 11:57:32 2019
InstallationDate: Installed on 2018-04-30 (266 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1812637

Title:
  systemd-resolved stops resolving

Status in systemd package in Ubuntu:
  New

Bug description:
  Regularly (= after about 15 mins of use) the systemd-resolved service
  stops resolving DNS names (any).

  Configuration:
  Two domains defined - one internal, one for external services
  DNS server does not provide DNSSEC services
  Both domains are in the search path (served by DHCP)

  Effect:
  Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins.

  Workaround:
  from the client CLI
  sudo systemctl restart systemd-resolved.service

  Background:
  A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC.

  I found discussions about "the correct way" DNS works (with only one
  domain).

  Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked
  fine).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10.6
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 11:57:32 2019
  InstallationDate: Installed on 2018-04-30 (266 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812637/+subscriptions

More information about the foundations-bugs mailing list