This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In my Azure AI Foundry project I have endpoints for Azure AI Foundry, Azure OpenAI, and Azure AI Services.
The DNS records for the AI Foundry and OpenAI endpoints resolve fine, but the Azure AI Services one (i.e. domain.cognitiveservices.azure.com) is not found in DNS.
I don't have this issue in my other projects in Azure AI Foundry, just that one.
Is there a way to get the host record generated / recreated?
Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 17%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Loryan Strant (MVP),
It looks like you are experiencing an issue where the Azure AI Services endpoint is not resolving in DNS, even though your other Azure AI Foundry and Azure OpenAI endpoints are working fine. This typically happens if there is a misconfiguration in DNS or private endpoint settings. As a first step, please verify your DNS configuration. If you are using Azure-provided DNS, the endpoint should resolve automatically. However, if you are using a custom DNS setup, you will need to confirm that the DNS servers are forwarding queries correctly. From a virtual machine within the same virtual network, you can run nslookup <your-endpoint> to check what DNS response you receive. If you have deployed the resource with a private endpoint, ensure that a Private DNS Zone is correctly linked to your virtual network and that the endpoint’s fully qualified domain name (FQDN) is registered with the right A record pointing to the private IP. If you are using a custom DNS solution, check that the forwarding rules are correctly mapping the cognitive services FQDN to its private IP address. In cases where the record is missing, you may need to manually create or update the A record in the Private DNS Zone. It is also important to confirm that there are no Network Security Group (NSG) rules or firewall settings blocking DNS queries or responses, as this can cause the resolution to fail.If needed, you can test connectivity using Azure Connection Monitor to verify that your environment can successfully connect to the private endpoint. If after these checks the DNS record still does not resolve, we recommend deleting and redeploying the Azure AI Services resource.This will trigger the creation of a fresh DNS record. If the issue persists even after redeployment, please open a support request so that we can investigate further at the platform level.For more information:
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns-integration
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-troubleshoot-secure-connection-workspace?view=azureml-api-2&source=recommendations
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
These are not my DNS host records to configure, they are provided by the service automatically when creating a project in Azure AI Foundry.
Hi Loryan Strant (MVP),
It appears that the DNS A-records for your private endpoint were not created correctly, which is causing the endpoint not to resolve. You can manually recreate these A-records in your Private DNS Zone to restore DNS resolution. Please follow the steps below:
privatelink.cognitiveservices.azure.com).vmantestcli).
10.0.0.4).
Once the correct A-records are added, the DNS resolution for your endpoint should work as expected.
For reference: Manage DNS records and record sets by using the Azure portal
Hello, I'm not sure what you are suggesting, because I don't own the azure.com domain, therefore cannot create host records for it.
Thank you for clarifying that issue here is ping < customvoicefqdn> is not giving public ip like the other Azure AI foundry hub project. (Only only ping at your side, could not proceed with nslookup)
Doing further tests and syncing with product group on it.
Thank you.
Issue here was one of your resources does not return public ip when pinged with domain URL (other one worked)
ping "<resourcename>.cognitiveservices.azure.com
Flushing the DNS cache ideally, should fix the issue
ipconfig /flushdns
If flushing DNS cache does not resolve the issue, we should use the healthy resource one which gives a public Ip when pinged.
Looking forward to hearing you.
Thank you
It would resolve it, if the issue was my end. However, the issue is not my PC or my network as the same issue has occurred on several different devices and networks.
I don't know what you mean by "use the health resource", as the DNS record of the endpoint is the DNS record of the endpoint. Using a "healthy resource" would mean using a different endpoint, which negates the problem.
Thanks for clarifying. That's what I suspected. Next time might I suggest you read the context of the question and understand the functionality before suggesting resolutions that don't apply.
Is possible to remove the old private endpoint and create new private endpoint. That way, it will re-provision the DNS records automatically.
We might need to modify A-records in Custom DNS server if it is Custom DNS scenario.
Thank you
Thank you for agreeing with fact that it is not possible to fix DNS records for sub resource for public Azure AI foundry.
Only suggested process would be creating new Azure AI foundry resource which gives public ips when pinged.
Thank you for your time and inputs on this matter.
Hi Loryan Strant (MVP),
Thank you for clarifying and you are absolutely correct that you do not and cannot create DNS records in the public azure.com domain.
The suggestion to add A-records applies only if your Azure AI Services resource is using a private endpoint. In that scenario, Azure creates a Private DNS Zone inside your subscription (for example, privatelink.cognitiveservices.azure.com) where you can create A-records that point to your private endpoint’s internal IP address. These private DNS zones exist only within your Azure environment, not in the public azure.com domain.
However, if your Azure AI Services resource is not using a private endpoint and you are relying on the public endpoint (for example, yourresource.cognitiveservices.azure.com), then you do not need to and cannot manually add DNS records. If the public endpoint is not resolving in DNS, it usually means that the DNS registration for that resource did not complete correctly during provisioning.
In this case, the recommended step is to delete and recreate the Azure AI Services resource. This will trigger Azure to provision the resource again and register a fresh public DNS record.