|
|
|
|
|
|
by viraptor
1009 days ago
|
|
|
If your ISP provides the ipv6 option but doesn't turn it on by default, turn in on. If they don't call them periodically and ask for IPv6 support. If you run only online service, enable ipv6 on it. Basically, help move the needle on the chicken and egg issue of adoption. Move more traffic to v6 as much as you have control over. |
|
|
Most content distribution networks (CDNs) support IPv6 even if the back-end is IPv4. For most web sites, a CDN is a good idea in general, so just use one.
For developers: don't hard-code IPv4 as an assumption. E.g.: don't validate network addresses with an IPv4-only regex, and don't store addresses into a 32-bit unsigned integer. Most SDKs and APIs have supported IPv4/IPv6 dual-mode addresses for like... two decades by default. Just don't... undo... all that effort!
Generally: Use DNS instead of IP addresses. Do it properly by respecting TTLs and using multiple upstream DNS servers in a fast failover configuration. This is not the default in many systems, especially Linux distros used in servers. Many admins "prefer" raw IP addresses because they think "DNS is unreliable". It isn't, it's just the default config that's poor.