fix file links

Author: cachai2

articles/container-apps/TOC.yml

@@ -388,7 +388,7 @@
     - name: Managing outbound connections with Azure Firewall
       href: use-azure-firewall.md
     - name: Private endpoints and DNS
-      href: private-endpoints-and-dns.md
+      href: private-endpoints-with-dns.md
     - name: Securing a custom VNET with an NSG
       href: firewall-integration.md
     - name: Tutorials

articles/container-apps/custom-domains-certificates.md

@@ -114,7 +114,7 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
 1. Once the operation is complete, you see your domain name in the list of custom domains with a status of *Secured*. Navigate to your domain to verify that it's accessible.
 
 > [!NOTE]
-> For container apps in internal Container Apps environments, [extra configuration](./private-endpoints-and-dns.md) is required to use custom domains with VNET-scope ingress.
+> For container apps in internal Container Apps environments, [extra configuration](./private-endpoints-with-dns.md) is required to use custom domains with VNET-scope ingress.
 
 ::: zone-end
 

articles/container-apps/troubleshooting.md

@@ -58,7 +58,7 @@ You can use the *diagnose and solve problems* tool to find issues with your cont
 If you receive an error message when you try to deploy a new revision, verify that Container Apps is able to pull your container image.
 
 - Ensure your container environment firewall isn't blocking access to the container registry. For more information, see [Control outbound traffic with user defined routes](./user-defined-routes.md).
-- If your existing VNet uses a custom DNS server instead of the default Azure-provided DNS server, verify your DNS server is configured correctly and that DNS lookup of the container registry doesn't fail. For more information, see [DNS](./private-endpoint-with-dns.md).
+- If your existing VNet uses a custom DNS server instead of the default Azure-provided DNS server, verify your DNS server is configured correctly and that DNS lookup of the container registry doesn't fail. For more information, see [DNS](./private-endpoints-with-dns.md).
 - If you used the Container Apps cloud build feature to generate a container image for you (see [Code-to-cloud path for Azure Container Apps](./code-to-cloud-options.md#new-to-containers), your image isn't publicly accessible, so this section doesn't apply.
 
 For a Docker container that can run as a console application, verify that your image is publicly accessible by running the following command in an elevated command prompt. Before you run this command, replace placeholders surrounded by `<>` with your values.

articles/container-apps/use-azure-firewall.md

@@ -60,4 +60,4 @@ Network rules allow or deny traffic based on the network and transport layer. Wh
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Configure a DNS for virtual networks in Azure Container Apps environments](private-endpoints-and-dns.md)
+> [Configure a DNS for virtual networks in Azure Container Apps environments](private-endpoints-with-dns.md)

articles/container-apps/vnet-custom.md

@@ -407,7 +407,7 @@ Remove-AzResourceGroup -Name $ResourceGroupName -Force
 
 ## Additional resources
 
-- To use VNet-scope ingress, you must set up [DNS](./private-endpoint-with-dns.md).
+- To use VNet-scope ingress, you must set up [DNS](./private-endpoints-with-dns.md).
 
 ## Next steps
 

articles/spring-apps/migration/migrate-to-azure-container-apps-network.md

@@ -126,15 +126,15 @@ For more information, see [Securing a custom VNET in Azure Container Apps with N
 
 Both Azure Spring Apps and Azure Container Apps support the use of custom DNS servers in a customer virtual network. We recommend adding Azure DNS IP `168.63.129.16` as the upstream DNS server in the custom DNS server.
 
-For more information, see [DNS for virtual networks in Azure Container Apps environments](../../container-apps/dns.md).
+For more information, see [DNS for virtual networks in Azure Container Apps environments](../../container-apps/private-endpoints-with-dns.md#dns).
 
 Currently, Azure Container Apps in a Consumption-only environment type doesn't support flushing DNS settings changes as Azure Spring Apps does. For more information, see [Flush DNS settings changes in Azure Spring Apps](../basic-standard/how-to-use-flush-dns-settings.md). However, the workload profile type of environment automatically refreshes DNS settings every 5 minutes.
 
 Azure Container Apps supports deployment with a private DNS zone. For more information, see the [Deploy with a private DNS](../../container-apps/vnet-custom.md#deploy-with-a-private-dns) section of [Provide a virtual network to an Azure Container Apps environment](../../container-apps/vnet-custom.md). This approach provides a more flexible way to support linking a private DNS zone than using Azure Spring Apps. For more information, see the [Link the private DNS zone with Azure Spring Apps](../basic-standard/access-app-virtual-network.md#link-the-private-dns-zone-with-azure-spring-apps) section of [Access an app in Azure Spring Apps in a virtual network](../basic-standard/access-app-virtual-network.md).
 
 ## Access an app in Azure Container Apps within a customer virtual network
 
-Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/dns.md) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
+Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/private-endpoints-with-dns.md) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
 
 - [Access an app in Azure Spring Apps in a virtual network](../basic-standard/access-app-virtual-network.md)
 - [Access applications using Azure Spring Apps Standard consumption and dedicated plan in a virtual network](../consumption-dedicated/quickstart-access-standard-consumption-within-virtual-network.md)

redirects/.openpublishing.redirection.sentinel.json

@@ -1261,7 +1261,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/sentinel/data-connectors/dns.md",
+            "source_path_from_root": "/articles/sentinel/data-connectors/private-endpoints-with-dns.md",
             "redirect_url": "/azure/sentinel/data-connectors/windows-dns-events-via-ama",
             "redirect_document_id": false
         },