Hello! Fresh install of Cachy. Going through system logs before I install anything to see what’s up and I see avahi-daemon saying “WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended.”
Threw that in to Gemini who said to confir mif systemd-resolved is active with “systemctl status sytemd-resolved”, and then see if it’s set to handle mDNS with “resolvectl status”. Yes to both.
From here it said to just disable mDNS by doing “sudo nano /etc/systemd/resolved.conf” and change “#MulticastDNS=yes” to remove the # and set it to no. Apparently even though it’s got a #, systemd is still pulling the default yes.
I’m not sure what potential issues I’m opening myself up to, if any, if I do this. Anyone have any insight?
They both compete for port 5353 (if I recall correct), which potentially makes mDNS unreliable (the warning, not so much critical). It basically depends on what your needs are (for advanced DNS-SD features or service announcements = avahi) and how many network services are active, but in general it’s safe to disable mDNS.
However, many prefer disabling avahi as systemd-resolved is the default DNS resolver (and optimized for netw.manager integration). I recall its prefered in Cachy-Wiki.
The avahi-daemon is often installed as a dependency (printer support during installation?), if so, you can safely disable its services.
In general it’s more convenient to keep avahi if you need mDNS service discovery (printers, etc).
If you keep mDNS check the config sudo nano /etc/systemd/resolved.conf and verify if MulticastDNS=yes.
If you keep avahi, multicast is no.
Let me know if you need support for commands to enable one over the other.