Comment by Spivak

> Although, in an enterprise setting, if you count DHCP reservations then that's what we do, having our whole office use them has greatly simplified our network configuration.

Pretty much my de-facto solution for networking, managing static IP's is a pain even with something like Puppet - one mistake with the configuration and I have to open up vCenter to get to the console and fix the configuration to get network connectivity. I literally use DHCP reservations for everything with the exception of intra-cluster communication for my PostgreSQL replicas (those are on a separate VMWare network and I manage those statically, but they never change).

> I could imagine a world where printers had a built-in DDNS client which would make them truly plug-and-play in an office but that's probably more complicated than it's worth.

This is what a DHCP hostname is for, no? My cheapie ASUS AC1900 at home uses the DHCP hostname from any device it allocates an IP address to as a local DNS alias, if I run `nslookup ls410d9a3.local 192.168.1.1` on any system on my home network it will point me to my Buffalo NAS (without needing multicast DNS, though that would still work as a fallback) - same for BRW142D2763B66E.local (which is my printer).

I could just as easily configure any dhcp server I use to automatically register DNS entries for new hosts if I wanted (probably in a separate DNS zone to prevent peoples phones from showing up in the default DNS search path).

> You mean just about every single home network?

Bingo!

No home user is going to statically assigns an IP to their printer on Wi-Fi; that would require a power user who even knows what that is.