[wharvle]

The typical behavior is that DNS returns an IPv6 address, then whatever-it-is sits there until a timeout, because it’s simply not being routed. I’ve not investigated further because turning off IPv6 fixes the problem and breaks nothing (that I care about). Anything that only returns an IPv4 address from DNS works either way.

My cellular connection supports IPv6, but testing sites report it’s misconfigured in a bunch of ways. I don’t see problems in practice, though. But on my home network, it’s turned off.

[vel0city]

This is what I was thinking about with the prefix issue. I've encountered this issue like twice and rebooting my router ended up with a different prefix, so it seems more like my router just didn't get the new prefix and thus kept handing out the old prefix to everyone with SLAAC and thus wouldn't get routed right.

[Dylan16807]

> because it’s simply not being routed

Well if you don't actually have IPv6, and you're turning off a broken ghost of IPv6, that's very reasonable.

But in that case it confuses people when you call that "turning off IPv6".

[wharvle]

Shrug Google’s router thinks I have it. And it’s on by default.