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.
Azure Elastic Private Link Traffic Filtering - Cannot Resolve Private Zone
Aiello, Lawrence
0
Reputation points
Hello,
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:
- The private link is accepted.
- The hostname "privatelink.eastus.azure.elastic-cloud.com" is resolving.
- The traffic filter is enabled in Elastic.
- 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?