I would like to scale back my hosting costs and migrate one (or a few) sites over to a machine that I host at home.

The bandwidth is more than enough to cover the traffic of these small sites.

The simplicity of IPv6 has attracted me to the idea of exposing that server over IPv6 for hosting, while my daily machines remain on the IPv4 side of the stack.

I don’t care if this means that the sites are reachable by fewer visitors, as the traffic has never been huge.

Am I going down a rabbit hole that I will later regret? How would you do this right?

  • @just_another_person
    link
    English
    42 days ago

    You’re going to be limited to what your upstream provider allows with regards to IPv6 traffic, if any at all. You’ll probably need an 4-to-6 or 6-to-4 translation somewhere, and that’s about it.

    • @cmeu
      link
      English
      11 day ago

      Agree it’s not that complicated Many ddns providers can update aaaa just as they do a records… Most isp should either be providing some range of native ipv6 addresses, or some kind of 4-to-6 translation. It’s 2024 - we’re beyond RFC 791 specs I find it helpful to deal with prefix delegation by providing a “token” for nmcli to use. Then the ddns script can locate your defined suffix and push it to to the host