2 ms·
> 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
by throw0101c 3y ago
> 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 3y agoI 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 3y agoAs 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/files * https://www.iana.org/domains/root/servers https://www.iana.org/domains/root/servers and bootstrapping the network infrastructure from there.