Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1240299 > unrolled thread

Bug#1101975: systemd-resolved: resolved no longer resolves mdns, despite being configured to

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1101975: systemd-resolved: resolved no longer resolves mdns, despite being configured to Herbert Snorrason <methanal@gmail.com> - 2025-04-03 12:30 +0200
    Bug#1101975: systemd-resolved: resolved no longer resolves mdns, despite being configured to Helmut Grohne <helmut@subdivi.de> - 2025-04-03 12:50 +0200
    Bug#1101975: systemd-resolved: resolved no longer resolves mdns, despite being configured to Russ Dill <russ.dill@gmail.com> - 2025-04-18 01:40 +0200

#1240299 — Bug#1101975: systemd-resolved: resolved no longer resolves mdns, despite being configured to

Package: systemd-resolved
Version: 257.4-9
Severity: normal
X-Debbugs-Cc: methanal@gmail.com

After an upgrade today, resolved appears to have stopped resolving mDNS queries,
despite previously having done so and still being configured to do so. This
appears to be the result of a new override file that appeared in the
package. Unlike multiple other changes that require action to maintain an
existing configuration, I did not get any sort of alert in the upgrade process.

I am aware that I can alter my configuration to override the override, but I do
have to wonder if it isn't more appropriate for the package to alter the default
configuration file than to override whatever is in the configuration file. At
the very least, it should be possible to alert users to the need for a
configuration change, rather than assuming that users will know why things have
broken.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.21-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-resolved depends on:
ii  dbus [default-dbus-system-bus]  1.16.2-2
ii  libc6                           2.41-6
ii  libssl3t64                      3.4.1-1
ii  libsystemd-shared               257.4-9
ii  systemd                         257.4-9

Versions of packages systemd-resolved recommends:
ii  libidn2-0          2.3.8-2
ii  libnss-myhostname  257.4-9
ii  libnss-resolve     257.4-9

Versions of packages systemd-resolved suggests:
ii  polkitd  126-2

-- Configuration Files:
/etc/systemd/resolved.conf changed:
[Resolve]
MulticastDNS=yes
LLMNR=no


-- no debconf information

[toc] | [next] | [standalone]

#1240301

Hi,

On Thu, Apr 03, 2025 at 10:21:07AM +0000, Herbert Snorrason wrote:
> After an upgrade today, resolved appears to have stopped resolving mDNS queries,
> despite previously having done so and still being configured to do so. This
> appears to be the result of a new override file that appeared in the
> package. Unlike multiple other changes that require action to maintain an
> existing configuration, I did not get any sort of alert in the upgrade process.

This is correct. The Debian Technical Committee asked the systemd
maintainers to disable mDNS support in the default configuration. The
chosen implementation was to place an override file.

> I am aware that I can alter my configuration to override the override, but I do
> have to wonder if it isn't more appropriate for the package to alter the default
> configuration file than to override whatever is in the configuration file. At
> the very least, it should be possible to alert users to the need for a
> configuration change, rather than assuming that users will know why things have
> broken.

The alternative of changing the default at compile time was the method
preferred by the Debian Technical Committee, but that was not acceptable
by the systemd maintainers.

I agree that the disablement deserves a NEWS fragment. Do you use
apt-listchanges to display such NEWS? Would that have made you aware of
the problem? Would adding a note to Debian's release notes help here?

Helmut

[toc] | [prev] | [next] | [standalone]

#1242514

> Hi,
>
> On Thu, Apr 03, 2025 at 10:21:07AM +0000, Herbert Snorrason wrote:
> > After an upgrade today, resolved appears to have stopped resolving mDNS queries,
> > despite previously having done so and still being configured to do so. This
> > appears to be the result of a new override file that appeared in the
> > package. Unlike multiple other changes that require action to maintain an
> > existing configuration, I did not get any sort of alert in the upgrade process.
>
> This is correct. The Debian Technical Committee asked the systemd
> maintainers to disable mDNS support in the default configuration. The
> chosen implementation was to place an override file.

The method of doing this is overriding the setting of
'MulticastDNS=yes' in the /etc/systemd/resolved.conf file. The only
way to get past this is to remove the override file, or create a
overriding override file in /etc/systemd/resolved.conf.d/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web