This site is supported by crabdance.com (freedns.afraid.org)
From their website, freedns.afraid.org/about-us:
About freeDNS: Paid & No-Charge Domain Hosting & DNS Hosting Services
About Us
The site FreeDNS began in 2001 because founder Joshua Anderson wanted to have fun with his domain hobby. He wanted to create a safe environment where other programmers could share domain names with one another at no cost, starting with friends. With that in mind, he launched the site from his domain AFRAID.ORG. In the beginning, like-minded tech lovers offered him a server and bandwidth to make his dream a reality. Over time, the site grew to include more members and more space was required. He realized that, in order to provide the same service to his growing list of users, he had to find a way to generate an income.
Like many Internet users, he wasn't a fan of advertising from day one. So rather than fill the site with third-party ads, as some free locations do, he created extra services that he could turn into a premium package. He knew these services had to offer individuals and businesses something they couldn't find elsewhere for the price. To this day, the paid subscription service of FreeDNS goes back into the company - be it promotion, research or just being a place technologists can explore their love of the web.
Josh has long enjoyed network operations and infrastructure scaling. Starting with only a single system, the premium support has been put toward creating a carefully selected geographically diverse network and infrastructure as only exclusively through premium support has made it possible to do. The entire network is now routinely processesing over 7 billion requests per month as seen on the [DNS Query Stats] page.
About the members
Our members have a range of backgrounds and projects from all walks of life, from enabling hobbyists and tinkerers to reach their home network from work (and vice versa), to designers and web developers, cloud developers, bloggers, to cutting edge VC backed startup companies, from congressional representatives to electrical co-ops, there have been manufacturing of multiple sorts, home (housing) builders, property developers, PC builders, electronics manufacturers to coffee shops, restaurants, and schools (classroom use) in US and abroad, there have been photographers, artists, entertainers, churches, and musicians/bands, robotics builders, chiropractors, realtors, insurance agents, flower shops, karate schools, PC game server operators (including minecraft)... and many many more.
[Sign up Free] [Premium Plans]
I was initially using DuckDNS (bokwoon.duckdns.org), but then CertMagic/Let's Encrypt kept complaining about their DNSSEC or something so I switched to a more reliable DNS provider.
From a reddit comment:
[–]throwaway234f32423df 3 points 3 months ago*
In addition to frequent outages, the DuckDNS servers are fundamentally and permanently broken in terms how how they handle DNSSEC queries
basically, when asked "does this hostname have DNSSEC", instead of saying "no", the DuckDNS servers just never respond, causing requests to hang and eventually time out
hence, DuckDNS hostnames are generally unresolvable through DNSSEC-aware resolvers; this is not a "sometimes" thing, this is how they always have been and probably always will be
ordinarily, for a hostname with no DNSSEC, the tester should complete in less than a second (Google for comparison) but with DuckDNS it takes it about 90 seconds and ends in multiple timeouts, meaning the absence of DNSSEC cannot be confirmed, meaning that a DNSSEC-validating resolver must return an error
tl;dr do not use DuckDNS, use literally anything else
better services: myaddr.tools, dynu.com, cloudns.be, noip.com, afraid.org, nic.us.kg
or just buy a numeric .xyz domain for $0.83/year(US) at Cloudflare Registrar and use the Cloudflare API (or a DDNS client that supports the Cloudflare API, as many of them do) to update DNS
This was the error I was seeing in my logs:
2025-06-02T02:48:30Z error renew could not get certificate from issuer {"identifier": "bokwoon.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "HTTP 400 urn:ietf:params:acme:error:dns - 188.245.55.41: Fetching https://bokwoon.duckdns.org/.well-known/acme-challenge/1f9VmhLjMROzSPYq7yFbFz_XmH5iSy7zDireuqL9Gnw: DNS problem: SERVFAIL looking up A for bokwoon.duckdns.org - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for bokwoon.duckdns.org - the domain's nameservers may be malfunctioning"}
2025-06-02T02:48:30Z error renew will retry {"error": "[bokwoon.duckdns.org] Renew: [bokwoon.duckdns.org] solving challenge: bokwoon.duckdns.org: [bokwoon.duckdns.org] authorization failed: HTTP 400 urn:ietf:params:acme:error:dns - 188.245.55.41: Fetching https://bokwoon.duckdns.org/.well-known/acme-challenge/1f9VmhLjMROzSPYq7yFbFz_XmH5iSy7zDireuqL9Gnw: DNS problem: SERVFAIL looking up A for bokwoon.duckdns.org - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for bokwoon.duckdns.org - the domain's nameservers may be malfunctioning (ca=https://acme-staging-v02.api.letsencrypt.org/directory)", "attempt": 5, "retrying_in": 600, "elapsed": 883.402851755, "max_duration": 2592000}
Since switching to freedns.afraid.org, I no longer see those errors in my logs.