debcrafters-packages team mailing list archive

[Wesley Hershberger <2078599@xxxxxxxxxxxxxxxxxx>]

Added the Debian bug I filed yesterday for reference [1].

@Lukas I'm wondering if "No DNS servers specified" is a result of [2] not coping well with the "@5003" in your unbound config. Using this instead gives the same error as the Debian bug:
# cat >> /etc/unbound/unbound.conf<< EOF

server:
    interface: 127.0.0.1
    interface: 10.1.2.3@5003
EOF

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106186
[2] https://salsa.debian.org/dns-team/unbound/-/blob/master/debian/unbound-helper?ref_type=heads#L36

-- 
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/2078599

Title:
  unbound-resolvconf.service fails in LXD

Status in Unbound - Caching DNS Resolver:
  New
Status in systemd package in Ubuntu:
  New
Status in unbound package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  after upgrading an LXD guest machine from 22.04 to 24.04.1, systemctl
  complains that units are failing:

  ● unbound-resolvconf.service loaded failed failed Unbound asyncronous
  resolvconf update helper

  Aug 31 19:19:25 install systemd[1]: Started unbound-resolvconf.service - Unbound asyncronous resolvconf update helper.
  Aug 31 19:19:25 install resolvconf[414]: Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
  Aug 31 19:19:25 install resolvconf[414]: No DNS servers specified, refusing operation.
  Aug 31 19:19:25 install systemd[1]: unbound-resolvconf.service: Main process exited, code=exited, status=1/FAILURE
  Aug 31 19:19:25 install systemd[1]: unbound-resolvconf.service: Failed with result 'exit-code'.


  
  # /usr/libexec/unbound-helper resolvconf_start

  Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
  No DNS servers specified, refusing operation.


  Looks like

  https://groups.google.com/g/linux.debian.bugs.dist/c/rdluvEnL6BE

  https://discuss.linuxcontainers.org/t/erratic-network-initialization-
  in-lxc-container-with-unbound-dns/18680

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: unbound 1.19.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudBuildName: server
  CloudSerial: 20221101.1
  Date: Sun Sep  1 02:17:43 2024
  SourcePackage: unbound
  UpgradeStatus: Upgraded to noble on 2024-08-31 (0 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/unbound/+bug/2078599/+subscriptions