-
Notifications
You must be signed in to change notification settings - Fork 20
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
dnsimple_zone_record Error: API returned a Validation Error for: value #165
Comments
Here is a response from DNSimple Customer Service
Don't know if this is correct but it does appear to be a server validation error. |
Hi @arenoir, thanks for your feedback. We're making some internal changes on how we store TXT/SPF records, to enhance our RFC compliance. In theory, the correct value for the TXT record (when DNS-serialized, which is what we accept there as input) is a quoted string:
hence your code should be:
Truth is, we've historically accepted both. We should continue to accept both for the foreseeable future. The team is investigating. |
Hi @weppos Thanks for the follow up. I assumed double quotes meant
Any thoughts or workaround would be greatly appreciated. Thanks |
Same issue here. But the value is in the dnsimple portal now: What can I do? |
It seems that the dnsimple API and the webfrontend works now differently as before. |
Hi @tzahari,
Actually, this behavior is correct. As per RFC, the RData of a TXT record should be encoded in quotes. If you look at the response from a dig query, that's more evident:
it is unfortunately common (and convenient) for TXT records (and a few others, such as HINFO and SPF) to colloquially refer to the non quoted version. And this leads to TXT implementations being notably inconsistent. We used to accept both quoted and non quoted version, and normalize the data behind the scenes with a best effort. But this led to some transformation ambiguity, and subtle bugs. Therefore, we are currently working to standardize the process and normalize values upfront so that what ends up being stored in the database, and transmitted to the public, is what our name servers will serve. This is the most common approach adopted by various DNS libraries and providers. We have decided for the time being to continue accepting a non well-formed value. Which means you can still provide us a quoted or non quoted version. But in either cases, we'll normalize it to the RFC-compliant, quoted version. We're working to publish additional documentation, and emails will go out this week to inform about some upcoming validation changes. |
Correct. New records are now being explicitly normalized to be RFC compliant. We'll be applying this normalization to all existing entries in the upcoming weeks, but before taking any actions we'll be sending out emails to inform customers. The only change we made so far is to make sure that new values are RFC compliant even if the input is not. |
@tzahari @arenoir regarding this particular report, we agree the change of behavior is a bug and we have identified the issue that is dependent to some Terraform expectations. The team is working to address the issue, and release a version that will continue to accept both well formed and non-well formed TXT values. We'll post updates on this ticket as soon as it's ready. We are on it right now. |
Hi @AGS4NO, it is now woking as expected! |
Hi @AGS4NO thanks for the quick fix! Everything is back in working order. |
First thanks for maintaining a terraform provider to the dnsimple service. We have been using it for over a year. We did recently upgrade from 0.11.1 to 1.3.0 but have not run into any issues until today.
We use the dnsimple provider to add the necessary txt records to our dns server in our CI/CD pipeline.
Today we received the following error when trying to apply our configuration to a new workspace (every PR creates a new terraform workspace).
The thing is nothing has changed with the configuration and the value is wrapped in double quotes.
Terraform Version
Terraform v1.6.2
on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Terraform should apply all changes and the txt record should be created
Actual Behavior
Terraform exits on apply and the txt record is not created.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: