Why You Shouldn't Worry About IPv6 Just Yet
nk497 writes "While it's definitely time to start thinking about IPv6, it's not time for most to move up to it, argues Steve Cassidy, saying most can turn it off in Windows 7 without causing any trouble. Many network experts argue we're nearing network armageddon, but they've been saying that for years.'This all started when Tony Blair was elected. The first time. Yep, that's how long IPv6 has been around, and it's quite a few weeks ago now.' He says smart engineering has avoided many of the problems. 'Is there an IPv6 "killer app" yet for smaller networks? No. Is there any reason based on security or ease of management — unless you're running a 100,000-seat network or a national-level ISP — for you to move up to it? No. Should you start to do a bit of reading about it? That's about the stage we're truly at, and the answer to that one is: yes,' he says."
the countdown to second economic Depression is half as many months away, so no worries. Those living in cities will be way too worried about from where the next meal is coming to give a shit about address space exhaustion.
That cruft and bloatware has to do with the basic design being poor... Windows 95 was so bad they had to ditch it and go to NT which while it offers some level of compatibility, is fundamentally different and can only achieve this compatibility in a rather crufty way...
Solaris on the other hand has kept the same basic design, and even the change from sunos 4.x to solaris (sunos 5.x) wasn't a huge one since both were still basically unix.
This is why windows often has multiple apis for doing basically the same thing, the original version was fundamentally flawed and couldn't be fixed, so it was replaced yet the old one remains because old apps still use it. Unix was better designed from the start so the apis can generally be extended or added to rather than replaced and duplicated.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
Until it changes, and you have to figure out why its not working and update it to the new address.
You've clearly never managed any network of any size or you'd know how incredibly stupid it is to use IP addresses when configuring things other than DNS and the default router, which you then proceed to do everything in your power to NEVER change the address of.
If you have a device that doesn't support DNS than you need to throw it in the trash, I don't care how small it is. I have $10 ethernet connectors that have built in TCP/IP stacks fully capable of doing DNS lookups that could be attached to an Atari 2600 with about 10 wires and would allow it to use DNS, IPv6 and IPv4 ... Its not like its hard to support, you just buy cheap shit.
I've moved several portions of our network to IPv6 without anyone even NOTICING thanks to DNS.
You're argument is that its easier to give 10 people an IP address than to use DNS and put the IP address in once ... I can not possibly understand how you came up with this thought.
You give your testing hosts 'special' non-obvious names so people don't have any more of a chance guessing them than they do an IP address.
What the fuck are you talking about? Yes if the DNS server goes down lookups are going to fail ... FOR EVERYTHING so its likely its not going to go down for long since that would essentially shutdown the entire network.
DNS servers tend not to break in case you haven't noticed, the server what is essentially static data. When they do break, you just restart the service and its a little slow until the cache builds back up with other hosts from external source but internal is instantly fast.
I'm not really sure what the hell you're talking about with the encryption stuff as I've never in my life heard of someone changing and encryption key and 'breaking dns' but I suppose with DNSSEC its bound to happen, its certainly not a problem that even NASA would have a concern about so you certainly have no real reason to worry.
If you're typing out an IP address more than once, you're doing it wrong, I don't care what you're doing.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager