I'd say if your DNS is broken, you've got much bigger issues as that'll break a lot more stuff. Unless your entire network is configured to use static IP addresses for
everything.
Quote:
|
Say you're testing a new/migrated/upgraded website without modifying the "live" site, by running it on an alternative IP.
|
I genuinely don't see why this is any different. Not unless you have bothered to memorise the IP addresses of both your hosts, the process is the same - you edit your hosts file to point to a different IP address.
Quote:
|
And no, I don't agree you can do that on IPv6 just as easily. Dealing with something like 2001::3fa5:7b:7b:7b:cf 2001::3fa5:7b:7b:7b:d0 2001::3fa5:7b:7b:7b:da really just isn't as comprehensible as 123.123.123.207 123.123.123.208 123.123.123.218
|
Maybe I'm just used to hexadecimal because I use it extensively in my day job. To me, you've got that first part that you'll possibly need to memorise but the rest is up to you to do as you please if you really want. All you end up with is something like this:
2001:0000:3fa5:7B::1
2001:0000:3fa5:7B::2
2001:0000:3fa5:7B::3
etc.
all the way up to...
2001:0000:3fa5:7B::ffff
That's not hard, surely?
I get that IPv6 autoconfig makes for completely unmemorable addresses but like with any infrastructure, you probably don't care about most end points and just want your servers to be static anyway.
And about the subnetting 512 addresses...well why bother? Take advantage of IPv6's stupid amounts of addresses and subnet it in a way that makes it even easier to remember:
2001:0000:3fa5:7B:1:1
2001:0000:3fa5:7B:2:1
2001:0000:3fa5:7B:3:1
Don't treat IPv6 like IPv4 and you'll find it's probably easier to work with.