25
submitted 2 months ago by zako@lemmy.world to c/selfhosted@lemmy.world

I feel that sometimes resolution of sub-domain.duckdns.org and host.sub-domain.duckdns.org fails with empty result or even timeout result. Tested resolution against Google and Cloudfare DNS servers.

Do you have a similar behaviour?

you are viewing a single comment's thread
view the rest of the comments
[-] Emotet@slrpnk.net 3 points 2 months ago

DuckDNS pretty often has problems and fails to propagate properly. It's not very good, especially with frequent IP changes.

[-] SidewaysHighways@lemmy.world 1 points 2 months ago

What's a better option these days? I'd be interested in trying to get rid of duckdns

[-] Emotet@slrpnk.net 4 points 2 months ago

Buying a domain. There might be some free services that, similar to DuckDNS in the beginning, work reliably for now. But IMHO they are not worth the potential headaches.

[-] zako@lemmy.world 2 points 2 months ago

I have a domain... but I think DynDNS is not always available for every domain or by every domain seller?

[-] 2xsaiko@discuss.tchncs.de 5 points 2 months ago

Registrars (or DNS providers if you don't use the one that comes with your registrar) worth using have an API to manage DNS entries. That's basically all there is to DynDNS.

[-] TVA@thebrainbin.org 2 points 2 months ago

Thats how I've done mine.

pfSense has an updater built in so that's handled my home.mydomain.com entry for me for a long time and has handled updating duckdns too, even though it's basically only a backup at this point.

If you've got a domain, no real reason to not just handle it yourself and avoid the headaches.

load more comments (4 replies)
this post was submitted on 02 Sep 2024
25 points (100.0% liked)

Selfhosted

39905 readers
294 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:

  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!

founded 1 year ago
MODERATORS