duckdns.org addresses seem problematic

I set up a new BQM. First of all I used my IPv4 and then I switched to my duckdns.org domain name. To my surprise the BQM stopped working properly - missing periods. You can see it here from this morning. If I use a ping service to resolve the name and ping my router it seems to be working but somehow not consistently for the BQM it seems.

I set up a new DDNS with https://freedns.afraid.org/ and that seems to be working fine.

Not sure what could be wrong with duckdns but anyway the freedns.afraid.org one seems to be fine so I'll stick with that.

In reply to a post by strubbly1:

I set up a new BQM. First of all I used my IPv4 and then I switched to my duckdns.org domain name. To my surprise the BQM stopped working properly - missing periods. You can see it here from this morning. If I use a ping service to resolve the name and ping my router it seems to be working but somehow not consistently for the BQM it seems.
I set up a new DDNS with https://freedns.afraid.org/ and that seems to be working fine.
Not sure what could be wrong with duckdns but anyway the freedns.afraid.org one seems to be fine so I'll stick with that.

I don't recall anyone mentioning this however I've just checked a load of duckdns monitors and all seem to have the same issue.
When I manually do the lookup it takes quite a long time to respond (seconds) whilst DynDNS doesn't have this problem, so I do think it's a DuckDNS issue.
Both services seem to have 60 second TTL (time-to-live) so it shouldn't behave any differently our end.

I just wrote a script and I'm seeing 100ms+ latency on DuckDNS responses (which still feels fast compared to manual 'dig') vs 5-6ms for DynDNS.

Hostname: xxx.duckdns.org, IP: x.x.x.x, TTL: 60, Response Time: 110.209 ms <-- yours
Hostname: xxx.duckdns.org, IP: x.x.x.x, TTL: 60, Response Time: 4343.93 ms
Hostname: xxx.duckdns.org, IP: x.x.x.x, TTL: 60, Response Time: 104.989 ms
Hostname: xxx.duckdns.org, IP: x.x.x.x, TTL: 60, Response Time: 903.929 ms
Hostname: xxx.duckdns.org, IP: x.x.x.x, TTL: 60, Response Time: 2735.466 ms

Hostname: xxx.dyndns.org, IP: x.x.x.x, TTL: 60, Response Time: 5.668 ms
Hostname: xxx.dyndns.org, IP: x.x.x.x, TTL: 60, Response Time: 4.866 ms
Hostname: xxx.dyndns.org, IP: x.x.x.x, TTL: 60, Response Time: 3.89 ms
Hostname: xxx.dyndns.org, IP: x.x.x.x, TTL: 60, Response Time: 4.448 ms
Hostname: xxx.dyndns.org, IP: x.x.x.x, TTL: 60, Response Time: 4.212 ms

Why it's so slow I don't know. I've done a trace and getting quick response from Afilias (Registry for .org) for DuckDNS nameservers, but DuckDNS.org's nameservers take the long response. ns3.duckdns.org is also down (in AWS).

seb

I don't know but I suspect maybe they are just under-provisioned/under-funded. Their business model is donations only so it is probably hard to keep everything going.

My alternative is working fine so no big deal for me but I thought it was worth pointing out to people who spot the missing data.

I only used duckdns for a short period last year and experienced similar hit-and-miss with both IPv4 and IPv6. The domain resolved for probably 4-5 hours per day maximum. Going from my experience I would say this is the new normal for duckdns.

In reply to a post by seb:

I don't recall anyone mentioning this however I've just checked a load of duckdns monitors and all seem to have the same issue.

I had similar issues with the free DDNS service built in to Asus routers. I also used Afraid.org and the problems went away.

I used duckdns for a while but had the same as you, large gaps. Unfortunately a side effect of a free service I think. I then bought a year's service from dyndns and had flawless service since.

I've now moved to a provider with static IP so no longer have a need, but it seems if you're on a paid service your results will be better.