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?

  • Shdwdrgn@mander.xyzEnglish
    11·
    1 month ago

    If you want to do it right, try to get a static IP (you may need to get a business account). If your provider doesn’t provide IPv6 to static IPs, go to some place like Hurricane Electric and get a free IPv6 range pointed to your IPv4 static address.

    Alternatively, you might do a search for any DDNS services that provide IPv6 (I’m not sure if any do?), then that service will fllow your residential address when it changes. Either way I think you’ll have some additional costs you need to weigh against your current hosting provider.

    • cmeu@lemmy.worldEnglish
      1·
      1 month 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

  • vinnymac@lemmy.worldEnglish
    2·
    1 month ago

    I’ve been doing this for the last 5 years using dynv6. Feel free to reach out if you need any help making it happen.