lobsters score: 2 · tags: networking
My approach is:
- DHCP all the things
- give them individual names that never change (granny names in my case)
- Find them using mDNS: device-name.local
- Find services they provide using DNS-SD; file servers are under _smb._tcp, speakers are _airplay._tcp, etc.
Minimal configuration, everything stays up to date with no manual work. What’s not to like?
score 3 · canonical
“guests” scanning your network easily and IoT devices (kef, tv, etc) sending a report of local services to the cloud… But yeah, I think it’s worth the risk for a SOHO.
score 1 · canonical
I struggled to get containers to be nice mDNS citizens, and I like them to be first class LAN members. Although I might give up on that
score 1 · canonical
I use an FQDN but otherwise my setup is similar. TXT records is a great idea. I use ULAs for lan-only-IPv6 and block the connections from the ULAs to the internet and vice-versa.
meta: To control dns, e.g. route53, records there’s this nice app called dnscontrol that is available through
pkg_add. Usingenvsubstand cron DNS record registration can be automated. I’m publishing service port names as well, but that will become a blogpost at some point (when time allows)…
score 1 · canonical