Add mDNS article #201
No reviewers
Labels
No labels
in progress
in progress
meeting
need info
ongoing work project
on hold
pending activity
release test
user documentation
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
server/user-documentation!201
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "brettweir/user-documentation:add-mdns-article"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR is a revised version of the write-up I did about mDNS as part of setting up a Raspberry Pi home server. I thought this might better serve as an article in the main server documentation.
All good, but I included some comments that might help improve this topic.
@ -0,0 +4,4 @@In this guide, we walk through making your server available by name on your local network via mDNS.This is useful in small networks, homelabs, or any other environment where clients exist on the same subnet as the server.Maybe expand this to note that if you have more complex networking like bridges for virtual machine networks or VLANs or multiple interfaces connected to different networks, you probably want to explore alternate DNS services, like DDNS etc.
I think this is good feedback, but I will leave it off for now, because I don't have a clear action in mind that they can take as a result of it, so it distracts from the article. I don't know much about DDNS at this moment, but I have some notes on Let's Encrypt and running your own domain that I will submit in a later article, at which point I think it makes sense to resurrect this note and link to that/those articles from here.
Created a follow-up ticket server/tickets#218
@ -0,0 +21,4 @@[source,console]----$ ping fedora.localping -c2 fedora.local
this avoids having to exit ping because it will drop out after 2 ping attempts.
I incorporated your suggestion (I did 3 because 3s are nice) and clarified the example to actually demonstrate that mDNS specifically is not working (because the machine is responding to ping via IP address).
@ -0,0 +53,4 @@TriggeredBy: ○ avahi-daemon.socket----It is disabled, so let's enable it:Your output shows it as enabled but inactive.
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
Updated in the latest commit.
@ -0,0 +95,4 @@[source,console]----$ sudo firewall-cmd --permanent --add-service=mdnssuccessI'm not sure the success output lines are valuable for these commands. This is present in other examples, but I think it just muddies a set of commands. Personally, I think we should remove outputs like this... but that also requires discussion and agreement on convention. And probably cleanup in other topics. Just noting here so that we can pursue this in channel.
Per discussion in Matrix, I will leave these in.