How does discovery work in fedora server?

submitted by

I can pull up cockpit by using the hostname in the web browsers url, but samba doesn’t point to the server by name. Only IP address pulls it up.

I don’t want to risk installing conflicting stuff but I’m not finding a lot of detail here. Does fedora have something for this included? Does it use avahi? Systemd-resolved? Smoke signals?

6
19

Log in to comment

Hot Top New Old

Your router is doing that, not Fedora Server.

 reply
3
OP

The router does not handle mdns discovery. That’s a Linux service. The router can answer questions from other clients but if has to be given the answer by the host in the first place. That’s what systemd-resolved and avahi do.

 reply
3

Doesn’t matter. Your machine going to another is not simply due to mdns running. In fact, I doubt that’s a default package selection in Fedora Server for security reasons, but I could be wrong.

Run dig [whateverhostname] from your machine, and then check /etc/systemd/resolved.conf on the server and see if something with MulticastDNS is enabled. Don’t see why that would ever exist as a default.

 reply
3

mdns (multicast DNS ) is specifically designed to work where a DNS server is presumed to not know hostnames, usually on a local network. So it is possible to use hostnames without a DNS server.

On fedora, discoverability of mdns should be on by default. Configuring mdns presence to others is a config away, if not enabled by default.

 reply
1

I’m aware of what it is. This is a Fedora Server install that shouldn’t have it enabled by default because it generally only fits the use-case of home users. Someone installing the default package list in an enterprise setting would not want this enabled.

I even checked to be certain, and it is not enabled by default.

 reply
3
Insert image