Cloudron Forum

@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.

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?