Azure Elastic Private Link Traffic Filtering - Cannot Resolve Private Zone

Aiello, Lawrence 0 Reputation points
2025-02-22T19:24:48.37+00:00

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:

  1. The private link is accepted.
  2. The hostname "privatelink.eastus.azure.elastic-cloud.com" 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 Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
537 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Aiello, Lawrence 0 Reputation points
    2025-02-22T21:25:51.09+00:00

    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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.