package nsd 4.1.26-1build1 failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1

Bug #1880795 reported by Maxime
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nsd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Just tried to install nsd package using apt: `sudo apt install nsd` and it has failed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nsd 4.1.26-1build1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
 libevent-2.1-7:amd64: Install
 libfstrm0:amd64: Install
 libprotobuf-c1:amd64: Install
 nsd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May 27 13:17:22 2020
ErrorMessage: installed nsd package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-03-23 (65 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: nsd
Title: package nsd 4.1.26-1build1 failed to install/upgrade: installed nsd package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Maxime (dp-maxime) wrote :
Revision history for this message
Maxime (dp-maxime) wrote :

Apparently, nsd package conflicts with systemd package (systemd-resolve, installed by default) on port 53, but neither package lists other one in Conflicts: section of package control file.

Revision history for this message
Maxime (dp-maxime) wrote :

By default, nsd binds to all local interfaces, and systemd-resolved provides stub listener on 127.0.0.53, so another solution would be in adding default configuration for nsd package to bind to 127.0.0.1 interface only.

Revision history for this message
Markus Schade (lp-markusschade) wrote :

Without any configuration NSD will automatically start and binds itself to port 53 on all available interfaces/ip addresses. It does not actually conflict with systemd-resolved if both services are configured explicitly. As a universe packages coming directly from Debian, its not tuned to Ubuntu defaults.

Changed in nsd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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