Selfhosted

39488 readers

292 users here now

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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Flaky dynamic IPv6-only DNS resolution (feddit.de)

submitted 1 year ago by skilltheamps@feddit.de to c/selfhosted@lemmy.world

1 comments fedilink hide all child comments

I have a problem with DNS resolution for my homeserver, and I'm wondering whether any of you experienced something similar or have any Idea what could be the problem. I have a IPv6 address only for my homeserver, no IPv4. I use https://dynv6.com for DNS. That means I have configured the router to transmit the IPv6-Prefix and created a AAAA subdomain-entry for the server, where I put in its MAC-address which dynv6.com uses to calculate the whole IPv6 address:

Now all that works in principle as it resolves to the correct address, but as you can see in the main image of the post, it does not work reliably. In that particularly bad example I used a DNS server from Google, and sometimes I just don't get any answer - same for other DNS services. I have been running dynv6.com for a year now, and this problem never went away.

Does anyone have an Idea what could be the problem? Could it be related to having just an AAAA entry, no A at all? Or how to debug something like this?

top 1 comments

sorted by: hot top controversial new old

[–] skilltheamps@feddit.de 0 points 1 year ago

Meanwhile I found the problem: it is dynv6.com itelf :(

Their 3 nameservers are not all responding with the same answer, in my case #2 claims to not have a AAAA record while #1 and #3 show the correct ip. It seems though I'm by far not the only one, and that this is not a new problem: https://community.dynv6.com/t/the-ns-1-3-dynv6-com-not-always-updated-with-my-public-ip-address/1107

I switched to another ipv6 dyndns provider, and all seems well now. So stay away from dynv6.com I guess. A shame really, as they have a really nice and intuitive UI, and seemingly also are the only ones that handle a ipv6-prefix for a whole zone...