-
Notifications
You must be signed in to change notification settings - Fork 30
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
Error if CAA 'iodef' record defined #73
Comments
I'm not sure why they're not merging it, but #66 has the fix you're looking for. |
Thanks, and good work! I have a case open with Namecheap and have passed this on. Fingers crossed they actually do something about it. |
I just tried to add the following records and failed with the error message below. I'm sure somehow the validation logic does not recognise Code record {
address = "0 issue \"pki.goog\""
hostname = "@"
mx_pref = 10
ttl = 1799
type = "CAA"
}
record {
address = "0 iodef \"mailto:[email protected]\""
hostname = "@"
mx_pref = 10
ttl = 1799
type = "CAA"
} Error│ Error: Records[18].Address "0 iodef "mailto:[email protected]"" must contain a protocol prefix for CAA iodef record locating the bugAfter adding the |
Update: if it's fully synced but you want to change any other part of the domain e.g. TXT _dmarc it wouldn't let you/me. |
The problemLine 40 in 5e44263
Line 193 in 5e44263
Suggested fixif strings.Contains(*record.Address, "iodef") && (!validURLProtocolPrefix.MatchString(*record.Address) && !strings.HasPrefix(*record.Address, "mailto:")) { |
Please give a try to the latest version of this provider released yesterday. |
Hi,
It seems if a zone in Namecheap contains a CAA 'iodef' record, the Namecheap Terraform provider fails to create DNS records. If the CAA record is removed, the creation succeeds. I've tested with A and CNAME records, using Terraform 1.4.0 and 1.4.6, with Namecheap provider 2.1.0.
Terraform Version
Terraform v1.4.6
Namecheap provider version
What version of terraform-provider-namecheap are you using? 2.1.0
Steps to Reproduce
The text was updated successfully, but these errors were encountered: