[p_l]

> Sorry, but that's a load of manure. It's not just about memorizing.

Ok, not just memorising. It's also the culture of cargo culted broken network designs, of excel spreadsheets from hell, of thinking everyone can memorise or put few post-its with IP addresses important to them so you don't need to care for DHCP and DNS or actually setting up routing instead of throwing a ton of NATed 10.0.0.0/8 or 192.168.0.0/24 then crying when there's a need to setup 5 layers of translation to connect two services (been there, done that, kept the scars).

As others pointed out, you should have anycast addresses for core network services (DNS at least).

IPv6 arguably even makes it easier because link-local automatic configuration actually works unlike v4 APIPA, well enough to discover and talk to other nodes on given L2. I still remember my happy surprise when HP ILOs used that to let me configure them over network by just connecting to same vlan, something I can't do on v4 without messing with DHCP rules.

The fact that link local actually works, combined with multicast and predefined multicast addresses like ff02::1 or the addresses for mDNS, DNS-SD, LLMNR etc mean that you can actually get somewhere without configuring IP on the link.

Do you need to learn new things, and possibly rearchitect the network? Sure. But it's because v4 was deficient.

Also, more often than not, the "it was DNS" involves "resolver not configured" or "put BS in DNS got BS back now crying".

> Like? I mean I avoid using MS where possible so I probably just haven't seen it but I'm quite curious what's dependent on it.

Essentially entire promise of DirectAccess, the transparent VPN system added in Vista, depends on the office network being IPv6-clean (as in, no user-used services that require v4 connectivity). Originally it required IPv6+IPsec connectivity at client side, due to lack of wide availability various fallbacks were added in Windows 7.

It's also why Vista and later had such a push to autoconfigure Teredo and similar V6 transition technologies.

[Control8894]

Should is not does, and also LOL @ anycast for some SMB's internal networking. Yeah, good luck with that bud.

> when it's broken it's broken cuz you broke it

No duh, but that doesn't make it any less broken.

[p_l]

"bad implementation and bad network design being easier to live with in v4" is not the winning argument you think it is.

Forcing the change seems to be the only way to fix some networks and some software, in fact.

> No duh, but that doesn't make it any less broken.

Nor does it make ones inability to ship minimal HOSTS file any less bad.