[mmh0000]

  > FWIW I really don't need to remember the IPv6 addresses of devices on my networks, DNS and my router handle that for me fairly automatically.

That is true, but the OP said the people manage the network equipment.

You do need to remember IPv6 addresses when your network is hosed when the DNS server becomes unresponsive or returns nonsense. IPv6 adds an annoying barrier to troubleshooting. Not that you can't work around it, but it does have more friction than troubleshooting IPv4 issues.

I'm personally really torn about IPv6. On one hand, it technically is better, and for more reason than just the increased address space. On the other hand, it is more difficult to grok than IPv4. Especially because IPv6 does a bunch of magic that, if you're not on high-end networking gear, isn't logged anywhere.

[throw0101c]

> You do need to remember IPv6 addresses when your network is hosed when the DNS server becomes unresponsive or returns nonsense.

Who is going to remember the IP addresses of all their switches, routers, and firewalls even when they are IPv4-only? I have less than a handful of switches, and have no idea what the IPs are.

Document the values (Netbox, MediaWiki, private company Github doc repo) and look them up if needed. Or put the values in the hosts(5) file of your management network bastion host(s).

[mmh0000]

I mean... I can remember, off the top of my head, IPv4 DNS servers: 1.1.1.1 4.2.2.2 9.9.9.9 and more! Those are pingable as well which is just great when troubleshooting IPv4

I'll be damned if I can remember a single public IPv6 DNS server.

[throw0101c]

As a sysadmin, I'd be more interested in getting DNS working internally, and then having the recursive resolvers simply following the pre-installed root hints file

* https://www.iana.org/domains/root/files

* https://www.iana.org/domains/root/servers

and bootstrapping the network infrastructure from there.