Question about new Galileo "Local Hostname Resolution" setting: systemd-resolved vs Avahi


I am following the Galileo changelog:

  • Local Hostname Resolution will be enabled on a new install – This was a community request to simplify the process to enable network printers described in our Discovery network printer article. Local Hostname Resolution being enabled doesn’t mean network printers are enabled by default, you still have to go through some steps to enable it manually.

This part links to the EndeavourOS Wiki Printers page which links to the Arch Wiki Avahi page

Now for my question: I am using an “older version” of EndeavourOS so I want to add mdns_minimal [NOTFOUND=return] to /etc/nsswitch.conf.

Do I also have to follow this part from the Arch Wiki?

Note: systemd-resolved has a built-in mDNS service, make sure to disable systemd-resolved’s multicast DNS resolver/responder (refer to resolved.conf(5)) or disable systemd-resolved.service entirely before using Avahi.

I am wondering why this is mentioned on the Arch Wiki but missing(?) in the EndeavourOS Wiki.

If I have to follow it, is it enough to add MulticastDNS=no to /etc/systemd/resolved.conf?

So I installed EndeavourOS Galileo on a different SSD for testing and noticed that systemd-resolved.service is disabled

$ systemctl status systemd-resolved.service
○ systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled)
     Active: inactive (dead)

I followed suit and also disabled it on my main system & skipped the “add MulticastDNS=no to /etc/systemd/resolved.conf” part.

Still unsure what’s the right thing to do…

You would only have to follow that part if you are using systemd-resolved. No problem to use systemd-resolved instead of (or in addition to) NetworkManager, but it does require additional configuration and is not enabled by default in EndeavourOS.

For what it’s worth, most people do not use systemd-resolved unless they have a specific networking setup that NetworkManager does not handle the way they need.

1 Like

Thank you for your response!

So I guess I must have changed something at some point for systemd-resolved to be active on my old EndeavourOS installation in the first place?

If it had been enabled, then yes. Perhaps you followed a guide online somewhere or something? By default it is not enabled.

Just to clarify: systemd-resolved is part of systemd, so it is “installed” by default so to speak. But to actually use it, it must be enabled, and additional configuration is required as well (at the very least setting up a symlink for /etc/resolv.conf).

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.