-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create MX records with "." as value #984
Comments
Thanks again @AlessioCasco; I just realised we shipped the fixes for cloudflare-go to understand the new data type but Terraform needs to change from |
Can you please try v2.19.1? I've just cut a release so it should be publicly available in the next 30-60 minutes . |
Many thanks, Jacob. |
I'm sorry to say this, but I'm unable to plan or to apply with 2.19.1 (reverting back to 2.19.0 works). During one apply attempt, terraform crashed with the following error:
|
gah. can you please provide your config and state so I can dig into this with a test case to match? |
I'll do it first thing tomorrow, it's quite late here in London :-) Thanks again |
sure, email it over to jacob.bednarz (at) hey.com |
rolling this over into #988 |
Sorry, Jacob, I'm going to send you the data tomorrow morning UK time. |
no worries! i'll see what i can do in the meantime as we have a few others experiencing this too. |
Hey @jacobbednarz, sorry to re-open this discussion, but this used to work for me until 3.14, now that I upgraded to 3.20 (with TF 1.2.6), I am getting the following error:
This is the resource resource "cloudflare_record" "mx" {
name = "@"
type = "MX"
value = "."
priority = 0
zone_id = data.cloudflare_zone.current.id
} If I can provide more info, or if I should open a new issue, please let me know. Thanks! |
We're having the same problem since upgrading. Existing records with I created them manually in the web UI, hoping that Terraform would recognize that they'd already been created and that no state changes were required, but it claims the records don't exist and wants to create them. |
Hi there,
It seems that we are still unable to create MX records with "." as a value (check #References for the first issue).
This is for protecting a parked domain setting up a null MX
Terraform version
Terraform v0.14.7
Affected resource(s)
Terraform configuration files
Debug output
https://gist.github.com/AlessioCasco/be4a674cfee5922c697d79cf9b64d10d
Expected behaviour
The MX record should be created with "." as value.
I am able to do it using the Cloudflare website
Actual behaviour
Terraform exits with an error:
Steps to reproduce
terraform apply
References
This issue was first reported in this issue: #944 and linked with #943
Community note
to the original issue to help the community and maintainers prioritize this request
request, please leave a comment
The text was updated successfully, but these errors were encountered: