Error Adding DNS Record to Azure DNS

Question

We started getting errors when trying to add CNAME DNS records to any of our domains in Azure DNS. Just started yesterday. Tried multiple computers, users, browsers, and clearing cache.

It still happens today. Simply cannot add any CNAME.

Error is blank. See screenshot.

Update: We can add the same CNAME via the CLI. Seems like the form is broken. To be clear the Error pops up, but is blank as shown in the screenshot. There is an error in the response.

"error":{"code":"LinkedInvalidPropertyId","message":"Property id '' at path 'properties.targetResource.id' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'."}}  

Update2: Please everyone following this thread up vote the question so it gets attention by the Azure team. It is definitely a UI update that created this problem.

Answer 1

Problem doesn't exist in preview portal:
https://preview.portal.azure.com

Answer 2

Same here. getting error on adding CNAME record for a subdomain.
content":{"error":{"code":"LinkedInvalidPropertyId","message":"Property id '' at path 'properties.targetResource.id' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'."}}
Can support share any ETA when this will be fixed?

Answer 3

I am also getting the same error since the Last User Interface update from Azure side

{"responses":[{"name":"388dda16-5c27-42c7-a703-36e33f9360f0","httpStatusCode":400,"headers":{"Pragma":"no-cache","x-ms-failure-cause":"gateway","x-ms-request-id":"178d48a0-dffe-4e6f-9fc9-6eb880afdb6f","x-ms-correlation-request-id":"6e48df4e-2fa9-4af5-8b90-e4ad42ff61ab","x-ms-routing-request-id":"CENTRALINDIA:20220623T133512Z:178d48a0-dffe-4e6f-9fc9-6eb880afdb6f","Strict-Transport-Security":"max-age=31536000; includeSubDomains","X-Content-Type-Options":"nosniff","Cache-Control":"no-cache","Date":"Thu, 23 Jun 2022 13:35:12 GMT"},"content":{"error":{"code":"LinkedInvalidPropertyId","message":"Property id '' at path 'properties.targetResource.id' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'."}},"contentLength":253}]}

Please help us to resolve this issue

Answer 4

We have exactly the same issue

Answer 5

Hi @Blane Bunderson @Calway @Sergejs Cerepanovs @Amuk Saxena @Anonymous

Thank you for asking this question on the **Microsoft Q&A Platform. **

The first thing I want to point out is that this problem is not because they are doing anything wrong.

I just escalated the issue with the Azure Support team who confirmed to me that it is working on the problem.

I will encourage you to create a support request if the issue persists.

Hope this helps,
Carlos Solís Salazar

----------

Accept Answer and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.

---