CNAME record conflict: Point "api" subdomain to AWS Load Balancer DNS

Solution

The CAA record added for AWS ACM certificate validation was the cause of the conflict.

Steps taken

  • The https://vercel.com/api/v4/domains/<my-vercel-domain>/records API endpoint includes the internal Vercel id for the DNS record.
{
    "records": [
        {
            "id": "rec_c625ccf17bfb13236fca932d",
            ...
            "name": "api",
            "type": "CAA",
            ...
        },
  • The CAA record had an ID that matched that shown in the error message in my original post.
  • I deleted the CAA record, and reattempted adding the new CNAME record for the ELB. The addition was successful.
1 Like