More control over DNS features.
-
Reoccuring problem with the automatic DNS features on Cloudron is that they will overwrite my MX records... so on one hand, it is really convenient that Cloudron can provision an A record, and it is really inconvenient that one click on the wrong button and it will overwrite my mx records.
It would be amazing if I could set restrictions allowing cloudron to write only A records and TXT records, leaving the MX for me to manage manually.
-
-
@murgero said in More control over DNS features.:
Cloudron shouldn't be touching any records that where already there.
At least not without warning first
-
@jdaviescoates
I can confirm that yesterday and many times before it wiped out my gmail mx records which is especially frustrating because I have cloudron mx records configured in google admin.Also, more reasonably it will overwrite an A record all day long.
In addition to that I have seen it overwrite my Dmarc policy which can be kinda annoying if you have dmarc records hosted through a tool like mx toolbox...
That is for both S3 and Cloudflare
-
@roofboard said in More control over DNS features.:
Also, more reasonably it will overwrite an A record all day long.
Personally I've always seen warnings before it overwrites any existing records.
-
@nebulon
Dynamic DNS is not enabled.
And yes there is manual intervention I could click "update dns settings" I am a little OCD and get frustrated staring at red dots because I have a custom configuration here and there.And just wish there was a way to tell cloudron "hey I know you think this record is wrong, but trust me its right and good" Or tell cloudron, "hey you can update A records and txt records but MX records those are off limits" or maybe a custom config file similar to a local hosts file where we could go in and take a record relationship and just straight up override it. This would enable configurations with load balancers, email routers, and hosted dmark utilities.
Normally I just set the DNS settings of Cloudron to manual, but I wish I did not have to do that. Especially because it always think I am wrong.
-
@roofboard said in More control over DNS features.:
Reoccuring problem with the automatic DNS features on Cloudron is that they will overwrite my MX records
We need to take a step back. Cloudron does not overwrite MX records. Can you tell me:
- Which DNS provider you are using?
- Can you confirm that email is not enabled for the domain in question on Cloudron ? Cloudron will only setup MX records if email is enabled for the domain.
- If email is enabled and for whatever reason you want MX to point elsewhere... I need to understand why you want email enabled but want the MX pointing elsewhere. Is this spam filtering related?
-
@girish
Which DNS provider you are using?- I am using cloudflare, but I have also had this issue with route53
Is email enabled. - Yes, my primary inboxes are google inboxes, but I have configured gmail to use cloudron as a catch-all email server using routing rules.
- On the subject of controls... I can also imagine situations where I would want to use a load balancer, or hosted spf service which again will trick Cloudron into thinking everything is set up wrong.
- I am using cloudflare, but I have also had this issue with route53
-
@roofboard said in More control over DNS features.:
Is email enabled.
Yes, my primary inboxes are google inboxes, but I have configured gmail to use cloudron as a catch-all email server using routing rules.I think this is what is confusing Cloudron code. Email is hosted outside Cloudron but Cloudron is also enabled as email server.
Do you think you can a post a screenshot or equivalent of how one configures gmail to use Cloudron as catch-all email server ?
Also, why exactly do you do this setup? Like one has to remember which mail server a mailbox resides in to login now?
