You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# namecheap_domain_records._dmarc-mx-TXT-id-6f170dfd-ba29-4af1-90f8-2308125247fa will be created
+ resource "namecheap_domain_records" "_dmarc-mx-TXT-id-6f170dfd-ba29-4af1-90f8-2308125247fa" {
+ domain = "[redacted].com"
+ email_type = "NONE"
+ id = (known after apply)
+ mode = "MERGE"
+ record {
+ address = "v=DMARC1; p=none"
+ hostname = "_dmarc.mx"
+ mx_pref = 10
+ ttl = 1799
+ type = "TXT"
}
}
# namecheap_domain_records.mx-A-id-6f170dfd-ba29-4af1-90f8-2308125247fa will be created
+ resource "namecheap_domain_records" "mx-A-id-6f170dfd-ba29-4af1-90f8-2308125247fa" {
+ domain = "[redacted].com"
+ email_type = "NONE"
+ id = (known after apply)
+ mode = "MERGE"
+ record {
+ address = (known after apply)
+ hostname = "mx"
+ mx_pref = 10
+ ttl = 1799
+ type = "A"
}
}
# namecheap_domain_records.mx-MX-id-6f170dfd-ba29-4af1-90f8-2308125247fa will be created
+ resource "namecheap_domain_records" "mx-MX-id-6f170dfd-ba29-4af1-90f8-2308125247fa" {
+ domain = "[redacted].com"
+ email_type = "MX"
+ id = (known after apply)
+ mode = "MERGE"
+ record {
+ address = "mx.[redacted].com."
+ hostname = "mx"
+ mx_pref = 10
+ ttl = 1799
+ type = "MX"
}
}
After accepting the actions, it appears that the MX record is properly created, but the other two records fail, with errors such as:
Error: Records[1].RecordType MX is not allowed for EmailType=NONE
with namecheap_domain_records.mx-A-id-6f170dfd-ba29-4af1-90f8-2308125247fa,
on [redacted]_plan.tf line 176, in resource "namecheap_domain_records" "mx-A-id-6f170dfd-ba29-4af1-90f8-2308125247fa":
176: resource "namecheap_domain_records" "mx-A-id-6f170dfd-ba29-4af1-90f8-2308125247fa" {
[X] Fatal Error: Terraform returned an error: No stderr was returned, this is likely a logic issue or partial error within the plan. (Example: if AWS, a bad AMI given the region)
This is with the current github version of Terry, commit dcf6861
The text was updated successfully, but these errors were encountered:
I was never able to fully get mailservers working. This is mainly due to the main email hosting providers (google, msft, etc) require you to use the SMTP relay of your chosen cloud provider. I have yet to have enough time to really dig into getting that built out and likely will not have the time to do that unfortunately :(
looking into my specific issue further, it looks like maybe namecheap requires that once you add an MX record, all new record add api calls require the RecordType parameter to be MX, even if you're only adding an A record. I'm not completely positive that's what's going on (and I've moved away from trying to use Terry for the mailserver for the time being) but it's what it looks like to me.
Could be a multitude of things. Ultimately, configuring mailservers is difficult given you must create the DNS records after creation of the infrastructure as the DMARC / DKIM records will rely on the keys generated on that host. I had gotten most of the skeleton for that built into Terry, but never got it finalized given the roadblocker of needing to use SMTP relays inside of each cloud provider
Attempting to add a mailserver to an existing operation using a namecheap domain is failing with an error.
command:
generates the following plan for dns resources:
After accepting the actions, it appears that the MX record is properly created, but the other two records fail, with errors such as:
This is with the current github version of Terry, commit dcf6861
The text was updated successfully, but these errors were encountered: