Ambiguity in mdns configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
I recently failed to get a 22.04 and 23.04 running reliably in a network with a cheap Huawei fiber router which provides routing and DHCP, but does not offer a DNS service with a zone with DHCP hosts. Therefore, machines cannot find each other by DNS.
Since mdns is designed to solve this problem (and I could remember that Ubuntu was dealing with such networks properly about 10 years ago), I tried to configure the machines to use mdns.
I was not able to get things running, since there are collisions between systemd/resolved on one hand, and avahi daemon on the other, colliding both on the UDP port and the functionality.
systemd/resolved are not really able to provide all services, but it is not possible to use avahi only either, since systemd/resolved is built so deeply into ubuntu, that it can't be removed or turned off without breaking lots of functionalities. Furthermore, I found systemd to be unreliable as an mdns resolver. Sometimes it works, sometimes it doesn't, sometimes it takes minutes.
I would have expected that Ubuntu would drop avahi daemon after moving to systemd, but now I found that 24.04 still comes with avahi daemon and competing functionalities.
E.g. avahi suggests to install libnss-mdns, while resolved wants mdns to be enabled in /etc/systemd/
So what is the suggested way to use Ubuntu in a network without proper DNS for DHCP-clients?
systemd+resolved? avahi? both?
I did not find any documentation about this, no simple configuration settings, no answer to the question how mdns should be used on Ubuntu since Ubuntu moved to systemd.
Nobody seems to care.
regards
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/2062927/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]