You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Are network security groups (NSG) enabled for private endpoints?](#are-network-security-groups-nsg-enabled-for-private-endpoints)
327
328
-[My private endpoint instance isn't in my VNet, so how is it associated with my VNet?](#my-private-endpoint-instance-isnt-in-my-vnet-so-how-is-it-associated-with-my-vnet)
328
329
330
+
### How do I connect to my cache with private endpoint?
331
+
332
+
Your application should connect to `<cachename>.redis.cache.windows.net` on port `6380`. We recommend avoiding the use of `<cachename>.privatelink.redis.cache.windows.net` in configuration or connection string.
333
+
334
+
A private DNS zone, named `*.privatelink.redis.cache.windows.net`, is automatically created in your subscription. The private DNS zone is vital for establishing the TLS connection with the private endpoint.
335
+
336
+
For more information, see [Azure services DNS zone configuration](/azure/private-link/private-endpoint-dns).
337
+
329
338
### Why can't I connect to a private endpoint?
330
339
331
340
- Private endpoints can't be used with your cache instance if your cache is already a VNet injected cache.
@@ -339,7 +348,7 @@ Trying to connect from the Azure portal console is an unsupported scenario where
339
348
340
349
### How do I verify if my private endpoint is configured correctly?
341
350
342
-
You can run a command like `nslookup` from within the VNet that is linked to the private endpoint to verify that the command resolves to the private IP address for the cache. The private IP address is found by selecting your **Private endpoint**from your resources. On the resource menu on the left, select **DNS configuration**. In the working pane on the right, you see the IP address for the **Network Interface**.
351
+
Go to **Overview** in the Resource menu on the portal. You see the **Host name**for your cache in the working pane. Run a command like `nslookup <hostname>`from within the VNet that is linked to the private endpoint to verify that the command resolves to the private IP address for the cache.
343
352
344
353
:::image type="content" source="media/cache-private-link/cache-private-ip-address.png" alt-text="In the Azure portal, private endpoint D N S settings.":::
345
354
@@ -374,7 +383,7 @@ Refer to our [migration guide](cache-vnet-migration.md) for different approaches
374
383
375
384
### How can I have multiple endpoints in different virtual networks?
376
385
377
-
To have multiple private endpoints in different virtual networks, the private DNS zone must be manually configured to the multiple virtual networks _before_ creating the private endpoint. For more information, see [Azure Private Endpoint DNS configuration](../private-link/private-endpoint-dns.md).
386
+
To have multiple private endpoints in different virtual networks, the private DNS zone must be manually configured to the multiple virtual networks *before* creating the private endpoint. For more information, see [Azure Private Endpoint DNS configuration](../private-link/private-endpoint-dns.md).
378
387
379
388
### What happens if I delete all the private endpoints on my cache?
380
389
@@ -393,4 +402,4 @@ It's only linked to your VNet. Because it's not in your VNet, NSG rules don't ne
393
402
## Next steps
394
403
395
404
- To learn more about Azure Private Link, see the [Azure Private Link documentation](../private-link/private-link-overview.md).
396
-
- To compare various network isolation options for your cache instance, see [Azure Cache for Redis network isolation options documentation](cache-network-isolation.md).
405
+
- To compare various network isolation options for your cache, see [Azure Cache for Redis network isolation options documentation](cache-network-isolation.md).
0 commit comments