this post was submitted on 02 Sep 2024
23 points (92.6% liked)

Selfhosted

60623 readers
595 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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 2 points 2 years ago (6 children)

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

[โ€“] zako@lemmy.world 1 points 2 years ago

In my case, there is no IP change. However, the TTL of entries seems to be 60 seconds and when Cloudfare/Google asks for the new A record, it sometimes fails. I am getting this error message from Cloudfare when I try to solve host.sub-domain.duckdns.org

EDE: 22 (No Reachable Authority): (time limit exceeded)

load more comments (5 replies)