{"level":"error","msg":"Failed to update TXT record named 'grafana' to '\"heritage=external-dns,external-dns/owner=*************,external-dns/resource=ingress/system/observability-grafana\"' for DNS zone 'myDNSZone.TLD': PUT https://management.azure.com/subscriptions/efa*****-****-****-****-************/resourceGroups/d-lock-rg/providers/Microsoft.Network/dnsZones/myDNSZone.TLD/TXT/grafana\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n \"code\": \"Conflict\",\n \"message\": \"The record could not be created because a CNAME record with the same name already exists in this zone.\",\n \"details\": [\n {\n \"code\": \"CannotCreateRecordDueToCNameNamingRestriction\",\n \"message\": \"The record could not be created because a CNAME record with the same name already exists in this zone.\"\n }\n ]\n}\n--------------------------------------------------------------------------------\n","time":"2024-11-07T10:39:12Z"}
so external dns would try to create this WRONG entries...
The CNAME cannot be created in Azure-DNS when providing the --default-targets="myfunnydummydomain.com"
External DNS creates the following entries...
Error Message:
{"level":"error","msg":"Failed to update TXT record named 'grafana' to '\"heritage=external-dns,external-dns/owner=*************,external-dns/resource=ingress/system/observability-grafana\"' for DNS zone 'myDNSZone.TLD': PUT https://management.azure.com/subscriptions/efa*****-****-****-****-************/resourceGroups/d-lock-rg/providers/Microsoft.Network/dnsZones/myDNSZone.TLD/TXT/grafana\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: Conflict\n--------------------------------------------------------------------------------\n{\n \"code\": \"Conflict\",\n \"message\": \"The record could not be created because a CNAME record with the same name already exists in this zone.\",\n \"details\": [\n {\n \"code\": \"CannotCreateRecordDueToCNameNamingRestriction\",\n \"message\": \"The record could not be created because a CNAME record with the same name already exists in this zone.\"\n }\n ]\n}\n--------------------------------------------------------------------------------\n","time":"2024-11-07T10:39:12Z"}so external dns would try to create this WRONG entries...