Here goes, installing a server with IPv6 only.. (because IPv4 costs more per month).. let's see how much stuff is broken!
@CenturyAvocado I guess success in that depends on how much it's used and by who and with what.
For internal stuff, yes. Public web server, without front end caching, or mail server without a friendly backup mx with IPv4, probably not.
@zymurgic the good news is.. everything I wanted to do worked fine. #Netbox installed and tinkered with. There's only one problem in their install documentation which is one of the tests has a command to bind to 0.0.0.0 which obviously didn't work when attempting to then access it over #IPv6. I had to figure out how to make it bind to v6 and not v4.
@CenturyAvocado @zymurgic servers are generally okay. You will want some kind of NAT64 for outgoing connections, and IPv4 for incoming reverse proxy (eg a CDN). The default config, like you found out, often isn't correct.
Home/personal computers are a lot worse, as there are things that just don't work, eg Steam.
