DuckDNS Domain Setup on Linode Server

[michuvon]

Hi,

I have cloudron running on a linode server and now got stuck on the Domain Setup page.

It's the first Linode server I'm setting up.
It's the first time I try Cloudron.
I have basic+ linux knowledge.
I wish to use duckDNS.

I have edited linux cron (following this guide: https://www.duckdns.org/install.jsp)

If I use my.duckdns.org domain, I already end up on the Cloudron Domain Setup page - it works.

On cloud.linode.com I have used the "Domains" tab on the left to add my duckdns.org domain and I can see A/AAAA Records for both *.my.duckdns.org. and my.duckdns.org

However, I tried using the Wildcard DNS Provider
but bet the error queryNs ENODATA my.duckdns.org

What I'm I doing wrong?

Not sure I understand correctly how to setup A records.
The docs assume me knowing this: https://docs.cloudron.io/domains/#wildcard-dns

Or can I just use No-op DNS as duckDNS and my linux cron edit solve this?

[michuvon]

@nebulon @scooke

I tried just using No-op DNS with the settings described in my initial post.

I now use my.mysubdomain.duckdns.org to get to the Cloudron dashboard.
and
pixelfed.mysubdomain.duckdns.org to reach my pixelfed instance.

Let's Encrypt worked and I do't get any error regarding SSL Certs from the browser, meaning https works.

---

However, I don't think that this step was actually necessary:

On cloud.linode.com I have used the "Domains" tab on the left to add my duckdns.org domain and I can see A/AAAA Records for both *.mysubdomain.duckdns.org. and mysubdomain.duckdns.org

---

NOTE: I realize that it was confusing to write my.duckdns.org as example URL, as cloudron is using my as subdomain for the panel.
I can't edit the original post any more, but if some day someone runs into the same issue and reads this post, be aware of it.

[scooke]

@michuvon Cloudron generally uses the entire system for itself, meaning it doesn't work well to install other apps or services outside the Cloudron. I don't think the documentation makes that clear enough, but that is probably because it assumes that since it is Docker-based that everything running on the server will be through it, Cloudron, using Docker.

You can use Searx version 1.6.0 in Cloudron, however. I don't know how they compare, but I saw the word, "privacy" in the description.

[nebulon]

I am not very familiar with duckdns, however I assumed you would have to choose a personal subdomain like foobar.duckns.org then further for the Cloudron dashboard you need my.foobar.duckdns.org pointing to your server and ideally the wildcard record as well, if they support this.

Further given that those are all subdomains of duckdns.org I am not sure if you will get an SSL certificate, since that domain might hit LetsEncrypt rate-limits quickly.

[michuvon]

@nebulon @scooke

I tried just using No-op DNS with the settings described in my initial post.

I now use my.mysubdomain.duckdns.org to get to the Cloudron dashboard.
and
pixelfed.mysubdomain.duckdns.org to reach my pixelfed instance.

Let's Encrypt worked and I do't get any error regarding SSL Certs from the browser, meaning https works.

---

However, I don't think that this step was actually necessary:

On cloud.linode.com I have used the "Domains" tab on the left to add my duckdns.org domain and I can see A/AAAA Records for both *.mysubdomain.duckdns.org. and mysubdomain.duckdns.org

---

NOTE: I realize that it was confusing to write my.duckdns.org as example URL, as cloudron is using my as subdomain for the panel.
I can't edit the original post any more, but if some day someone runs into the same issue and reads this post, be aware of it.

[stokito]

The DuckDNS.org is the most popular way to get a domain for free and it's extremely important for selfhosting.
From what I saw in sources the Cloudron has own implementation of the ACME DNS challenge. The problem is that each DNS provider has own API incompatible with others.

The Sandstorm.io instead uses the library https://github.com/therootcompany/acme.js which was also developed for a selfhosting project. The library has support of many providers including the DuckDNS.

As an alternative solution may be acme.sh which is not in JS but in plain shell instead. It has support of probably all possible DNS providers.

Interesting that the Sandstorm doesn't support setting of a custom domain but instead use it's own DDNS service sandcats.io The service is not that good and doesn't support setting of TXT or MX records.
I'm working now on writing a DDNS server that can be deployed https://github.com/yurt-page/go-ddnsd. There is already one existing called https://github.com/nsupdate-info/nsupdate.info which supports users registration. But I wish to make something more lightweight and simpler with autoregistration and I'll continue later.

You guys can try to deploy the DDNS server and autoregister new cloudron installs and give a free subdomains.
This will help a lot for selfhosters.