@KISSmyOS@lemmy.world
link
fedilink
English
31Y

The modern solution would be buying a domain and pointing the AAAA-record to your server’s ipv6 address.

@TCB13@lemmy.world
link
fedilink
English
51Y

… that may change at any time.

@KISSmyOS@lemmy.world
link
fedilink
English
31Y

If your provider keeps changing your ipv6 prefix, then you still need dyndns.
With a static prefix, you don’t.

@Auli@lemmy.ca
link
fedilink
English
21Y

No I just have a service that waits for the up to change and when it does it runs a script that updates my AAAA record.

@zaphod@lemmy.ca
link
fedilink
English
11Y

Not if you use a Hurricane Electric tunnel for ipv6 transit. My ISP hands out V6 addresses and I still use HE so I get a stable, globally routable /48 that moves with me (I had to switch ISPs recently and I just had to update my tunnel and everything just worked).

@TCB13@lemmy.world
link
fedilink
English
11Y

True, but that goes back to the irony of “I want to selfhost, and therefore I need a service provider…”, in this case HE. And won’t take of the IPv4 issue, we can’t just assume every network we use to connect to a home setup will be IPv6 capable. At that point you can just pick a Cloudflare tunnel and have it all working.

@4am@lemm.ee
link
fedilink
English
11Y

IPv6 typically assigns blocks to endpoints, not single WAN IPs (ie there is no NAT).

Changing this often would be absolute chaos for all connected devices, even if they’re configured correctly.

@TCB13@lemmy.world
link
fedilink
English
1
edit-2
1Y

Yes ISPs do assign IPv6 blocks via Prefix Delegation, the thing is that Prefix Delegation is done over DHCP. They’ll assign a block and if your router/device is restarts they’ll just give you a new prefix. In some even more annoying cases you can even get a new prefix whenever the lease expires.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 129 users / day
  • 423 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog