elasticsearch - Azure Elastic Private Link Traffic Filtering - Cannot Resolve Private Zone - Stack Overflow

admin管理员组

文章数量:1287800

I am attempting to set up Private Link Traffic Filtering with Azure and Elastic. I have completed steps 1, 2, 3, and 4 of this document. I have confirmed the following:

1. The private link is accepted.
2. The hostname "privatelink.eastus.azure.elastic-cloud" is resolving.
3. The traffic filter is enabled in Elastic.
4. I have configured the traffic filter to my specific deployment in Elastic.

At the end of part 4 however, none of the tests that I am doing seem to work. I keep getting "could not resolve hostname" of the specific deployment I am trying to hit. I have tried both the alias and the cluster ID methods, neither are working. How do I get this to work?

I am attempting to set up Private Link Traffic Filtering with Azure and Elastic. I have completed steps 1, 2, 3, and 4 of this document. I have confirmed the following:

1. The private link is accepted.
2. The hostname "privatelink.eastus.azure.elastic-cloud" is resolving.
3. The traffic filter is enabled in Elastic.
4. I have configured the traffic filter to my specific deployment in Elastic.

At the end of part 4 however, none of the tests that I am doing seem to work. I keep getting "could not resolve hostname" of the specific deployment I am trying to hit. I have tried both the alias and the cluster ID methods, neither are working. How do I get this to work?

• azure
• elasticsearch
• azure-private-link
• azure-private-dns

Share Improve this question Follow asked Feb 22 at 19:27 Lawrence AielloLawrence Aiello 4,65855 gold badges2222 silver badges3737 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Resolved my issue. It ended up being that the A record I created in the private DNS Zone had the name of "@" instead of "*". Fixing that resolved my problem.

本文标签： elasticsearchAzure Elastic Private Link Traffic FilteringCannot Resolve Private ZoneStack Overflow