Cloudron Forum

Good suggestion. For future reference:

The current zen spamhaus check only covers SBL, SBLCSS, XBL and PBL blocklists. To query DBL, one can do host domain.com.dbl.spamhaus.org 127.0.0.1 on cloudron . Would be good to get this automated like the zen check

Ok. I will doublecheck this. Give me a few hours for this.
Thanks for the moment 🙂

Update: Solution work fine! Thanks a lot. 👍

@jdaviescoates said in Installed at map.bridport.coop then deleted, then reinstalled on same location: server not found:

Is there a way to flush the NXDOMAIN cache on routers/ computers?

Not that I am aware of. These days browsers also do their own DNS caching complicating things even more.

@matthewdykstra issue is somewhere on the DNS side. Is that domain using Cloudflare? If so, for a start I would disable Cloudflare proxying for my.mjsiebolt.pro and just make that point to your server (so a single A record). Once that starts working, you can re-enable Cloudflare proxying and see.

@girish said in Cloudron often having problems with connection, "DNS_PROBE_FINISHED_NXDOMAIN", connection times out:

sudo nano /etc/hosts

thanks girish!!!

@briankb-0 said in Root Domain Hosts Shopify Site Subs Are Cloundron:

What happens if I add the domain to Cloundron so I can use it to setup sub-domains for NodeBB and Ghost?

When you add a domain:

To validate credentials, the code will add a cloudrontestdns A record and remove this immediately. To configure the server to send emails: If there is an existing SPF record, it is edited to have a:my.my.domain.com . The SPF record essentially whitelists which servers can send email on behalf of the domain. This is NOT destructive, your existing SPF record is only amended. A DKIM record is added under <random>._domainkey.domain.com. This is used to sign/verify emails by mail servers. Because of the 'random' part, it won't conflict with any of your existing DKIM keys If there is no existing DMARC record, we create one with the value "v=DMARC1; p=reject; pct=100". This essentially is a strict DMARC policy not allowing anyone outside the SPF record to send emails on behalf of the domain.

Other than that, it is what @BrutalBirdie said. The bare/root domain is untouched. Cloudron only adds entries when you install apps. Also, if you had a root domain DNS entry already, it will warn you that it's in use, if you try to install an app on the root domain (it does this check for any subdomain).

@humptydumpty Err, I forgot that I already removed those last week as well - https://git.cloudron.io/cloudron/dashboard/-/commit/72ba61ad91d326c3f287a2f538809cc78afcfdc8 . So, this should be fixed in next release.

@LoudLemur looks like the DNS record was pointing to a Cloudron which didn't have any app installed on that (sub)domain. If a Cloudron server as such just gets deleted, then the DNS records are not automatically cleaned up, since there is nothing running anymore to do that.