Am 18.05.20 um 18:02 schrieb David Bremner: > Package: network-manager > Version: 1.24.0-1 > Severity: normal > > In order to get MulticastDNS working with nm and systemd-resolved, I had to > set > > connection.mdns=1 # for 'resolve' > connection.mdns=2 # for 'yes' > > I'm not sure if I missed something about the config file format. From > the documentation it seemed that
Which documentation? > connection.mdns=yes > > should work, but it did not (i.e. resolvectl status did not show MDNS > enabled, and resolvectl query foo.local fails) man 5 nm-settings [1] has > │mdns │ int32 │ -1 > │ Whether mDNS is enabled for │ > │ │ │ > │ the connection. The permitted │ > │ │ │ > │ values are: "yes" (2) │ > │ │ │ > │ register hostname and │ > │ │ │ > │ resolving for the connection, │ > │ │ │ > │ "no" (0) disable mDNS for the │ > │ │ │ > │ interface, "resolve" (1) do │ > │ │ │ > │ not register hostname but │ > │ │ │ > │ allow resolving of mDNS host │ > │ │ │ > │ names and "default" (-1) to │ > │ │ │ > │ allow lookup of a global │ > │ │ │ > │ default in │ > │ │ │ > │ NetworkManager.conf. If │ > │ │ │ > │ unspecified, "default" │ > │ │ │ > │ ultimately depends on the DNS │ > │ │ │ > │ plugin (which for │ > │ │ │ > │ systemd-resolved currently │ > │ │ │ > │ means "no"). This feature │ > │ │ │ > │ requires a plugin which │ > │ │ │ > │ supports mDNS. Otherwise the │ > │ │ │ > │ setting has no effect. One │ > │ │ │ > │ such plugin is │ > │ │ │ > │ dns-systemd-resolved. which seems consistent with what you did. [1] https://manpages.debian.org/buster/network-manager/nm-settings.5.en.html unfortunately has broken formatting
signature.asc
Description: OpenPGP digital signature
