debcrafters-packages team mailing list archive

[Nick Rosbrook <2120756@xxxxxxxxxxxxxxxxxx>]

Can you please provide some basic instructions on how to replicate your
setup, and how to reproduce the issue?

There is nothing in the systemd updates between 255.4-1ubuntu8.8 and
255.4-1ubuntu8.10 that *should* affect DNS, but never say never.

> A tcpdump revealed, that borg backup was not using 127.0.0.53
(systemd) DNS, but 127.0.0.11 DNS server from docker (which was not
responding).

This seems to suggest it's not a systemd problem, no?

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

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

Title:
  DNS problems with borgbackup after systemd update

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After updating from systemd 255.4-1ubuntu8.8 to 255.4-1ubuntu8.10, I
  can no longer run borg backup on my host:

  ----
  Remote: ssh: Could not resolve hostname ****: Temporary failure in name resolution
  ----

  However, if I do SSH directly, it works as it should.

  I have docker installed on this machine.

  A tcpdump revealed, that borg backup was not using 127.0.0.53
  (systemd) DNS, but 127.0.0.11 DNS server from docker (which was not
  responding).

  Note: I hope that this is correct, as I have already downgraded
  systemd back to version 255.4-1ubuntu8.8. I'm not 100% sure about the
  addresses being used, but I'm sure that a different IP starting with
  127.0.0.x was used and it did not respond to the queries. Funny
  enough, when I started the borg process using strace, it worked as
  well.

  After a systemd downgrade back to 255.4-1ubuntu8.8, the problem no
  longer occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu8.10
  ProcVersionSignature: Ubuntu 6.8.0-71.71-generic 6.8.12
  Uname: Linux 6.8.0-71-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Sat Aug 16 14:41:01 2025
  InstallationDate: Installed on 2022-04-22 (1212 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
       |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: OpenStack Foundation OpenStack Nova
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-71-generic root=/dev/mapper/vgk006589vsa-root ro nomodeset
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2025-01-01 (227 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr18.2.2:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 18.2.2
  dmi.sys.vendor: OpenStack Foundation

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