Tell your network to explain itself and then some
22 points by confusedalex
22 points by confusedalex
My approach is:
Minimal configuration, everything stays up to date with no manual work. What's not to like?
"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.
Nothing! I also like adding static DHCP maps/reservations so the IPs never change either but you get all the client-name stuff and everything you just said too.
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
Oh wow, I felt very honored being quoted! 😅 But you are 100% right, a DHCP server that is able also interact with a DNS server is the way to go!
I have all my DHCP and DNS handled by RouterOS in my MikroTik router and also Adguard DNS as internet sanitizer...
What I absolutely loved from ARP is being able to map an unknown network quickly. I'm gonna take over managing the network of a small organization, and there little to no documentation... arp-scan is likely one of the first commands I'll run there!
A thing with arp-scan, it needs it's manufacturers database updated. It comes with get-oui, but IEEE broke it by disabling downloading the required files with scripts. It's simple enough to download the files, modify the script and run it. arp-scan is way more useful if the manufacturers column is not just a bunch of (unknown)!
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. Using envsubst and 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)...