CAA is not supported

Question

CAA is not supported

kzapolski opened this issue 5 years ago · 10 comments

Importing works fine, but when after that trying plan it fails with:

Error: type must be one of: [A AAAA CNAME MX NS SOA TXT]

Answer 1 · 2020-01-03T13:13:17.000Z

I think the problem is with GoDaddy API DNSRecord here https://developer.godaddy.com/doc/endpoint/domains#/

type* : string
    Enum:[ A, AAAA, CNAME, MX, NS, SOA, SRV, TXT ]

Answer 2 · 2020-02-26T02:40:39.000Z

@kzapolski / @Nenzyz - could you confirm whether or not this behavior is still occurring for you with the latest release?

Answer 3 · 2020-02-26T08:18:52.000Z

Sorry but I can't confirm nor decline.
I made my own version of the plugin with CAA included and it was working fine.
The issue is that plugin or better say Godaddy API is so unusable, you have to specify the whole zone in order to not overwrite what is not mentioned.
There is no possibility to use "count" on records so I gave up using it and just doing manual updates.
My fork of repository has all necessary changes.

Answer 4 · 2020-03-31T18:24:19.000Z

I'm still seeing this in 1.7.1

Answer 5 · 2020-03-31T18:29:36.000Z

Steps to reproduce:

Define a CAA record for a domain
Import that domain
The plugin becomes unusable

Answer 6 · 2020-03-31T18:32:50.000Z

You might want to add this patch.

Answer 7 · 2020-04-02T01:19:18.000Z

Hey @conet - thanks for the report. @Nenzyz, thanks for the patch. 🙏

Answer 8 · 2020-04-02T07:58:20.000Z

@n3integration you are welcome, keep in mind as long as CAA is not allowed to be changed, it should be added to isDisallowed(.., ..) list. It is in the patch also.

Answer 9 · 2020-04-02T08:31:01.000Z

Without adding CAA to the isDisallowed list, this error is encountered when applying:

Error: [422:INVALID_BODY] Request body doesn't fulfill schema, see details in `fields` (records[0].type [INVALID_VALUE]: is not one of enum values: "A", "AAAA", "CNAME", "MX", "NS", "SRV", "TXT")

Answer 10 · 2020-04-02T08:38:40.000Z

Also because of the way the API works and the resource declaration models this (there is no API to delete one record) it would be nice if only real differences could be shown when deleting a record from the middle of the list of records.