Cloudron Forum

@scooke yes, you can mix between Cloudron's automation and manual DNS changes. In fact, that's the normal and only mode of operation. The automation is only adding and removing things that you would have to do normally outside Cloudron. For example, when you install an app, you have to setup A records. When you uninstall an app, you remove the A records. This is all the automation does. If you try to install an app in a location and there is already a DNS entry in your DNS provider, Cloudron will inform you of the same and let you 'overwrite' it or cancel the app installation. Same goes for email stuff. It sets up things like DKIM/SPF records automatically. These are updated carefully to not collide with existing entries. The MX record is only touch if you enable incoming Cloudron Email. Even in that case, there is a checkbox to not update DNS.

@khadanja Is your idea to forward all queries ? The example config you pasted will only forward DNS queries for cloudron.lan (sic). You need the config in https://forum.cloudron.io/topic/5756/custom-dns-server-in-local-network/2 to forward all queries to your router.

@SignalScout On the server, please try host -t NS example.com 127.0.0.1 . Does that work? Sometimes, it takes a bit for the NS of a new domain to propagate. One just has to wait it out.

@murgero I didn't say it wouldn't be accessible; it would, just through my proxies, that make sure to remove any information, that would help in disclosure. You also miss an option with Intranets.

@klfc556 let's follow up at https://forum.cloudron.io/topic/5715/domain-setup-shows-queryns-eservfail

@brutalbirdie ok, thank you - I've got the idea!

If you like you can send us your domain name to support@cloudron.io and we can check if it's something on your side (i.e. some browser caching issue) or if we see it as well.

@girish Thanks, I thought maybe I set the DNS wrong but it must be the host then

Problem solved by install all three instances into one and bought a license from cloudron. Now it works

@d19dotca Okay, that is a bit confusing, but I will only be able to figure it out once I try it. I appreciate everyone's help and responses.

I had the same issue and I was able to follow the steps given about setting up a redirection in Cloudron. In fact, I decided to write a full article about it to help others understand how to fix this issue step by step. You will have to make sure you put the right DNS entries and then set up the redirection. Read this guide here and it will help you to fix this issue.

@mastadamus right, the spamlists won't work if those lookups get blocked. Currently, if the lookups fail, the mail server will simply go ahead and try to detect spam via spamassassin. It's just one of the metrics for spam detection. I guess it's fine if it's working OK for you without it .

@girish Just when I thought I understood DNS I learn about negative caching. Not sure if this was the issue, but it is possible. Thanks.

@girish No I've not patched manually, I have assumed sorry I assumed the latest update was with the CNAME/A-record fix was live. The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4. After that the DNS propagation didnt work any longer, as it had done before.

I'm sorry I missed that post. Maybe both can be merged, since my post provides an actual link to the API documentation?

Nope, there's no AAAA record, just an "A+ Dynamic DNS Record" Incidentally, I'm about to switch this domain to Hetzner, in any event. Namecheap is ok but also quite annoying from time to time...

@meaculpa hehe I was just about to comment here, since I wasn't able to reproduce it on my side. Glad it worked out now for you. Always good to have such topic for others to find if they hit the same issue in the future.

a restart dit the trick! thank you.

@atrilahiji said in Installation gets stuck in "checking DNS" step: @jakobgreenfeld Oh I missed the bit where theres only a txt record. Add an A record pointing my.domain.com to your IP. I've had nothing but trouble with Namecheap's API for configuring everything so I've started doing this: A record for *.domain.com A record for @ That did the trick! It's working now. Thanks!