The DNS service on my on-premise VM is not able to resolve the inbound endpoint in my DNS Private Resolver

Question

The DNS service on my on-premise VM is not able to resolve the inbound endpoint in my DNS Private Resolver

Colin Gilchrist 0

I have a on-prem server with DNS services enabled that I am trying to configure conditional forwarding on with my inbound endpoint from my private resolver. The on-prem server is on a network that has a functioning S2S tunnel to my Azure Vnet. I have a Azure private DNS zone that was generated when creating a private endpoint, linked to the VNET.

From the on-prem server I can telnet to the inbound endpoint on port 53, and I have confirmed that port 53 is open on my on-prem network. Even though I have network visibility into the inbound endpoint and can confirmed that port 53 is open, I am still unable to resolve the inbound endpoint IP. I have tried using a conditional forwarder using the domain of the private DNS zone, and I have also just tried adding the inbound endpoint as a standard forwarder, and it cannot resolve.

I feel I have this configured exactly as described in documentation and recommended guides, and have exhausted a large number of troubleshooting options. Does anyone have any ideas? Please let me know if additional details are needed.

G Sree Vidya 255 Reputation points Microsoft External Staff

2025-03-10T01:35:04.1133333+00:00

Hello Colin Gilchrist,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
G Sree Vidya 255 Reputation points Microsoft External Staff

2025-03-11T01:34:18.1866667+00:00

Hello Colin Gilchrist,

Following up to see if the below suggestion was helpful. And, if you have any further query do let us know.

1 answer

Your answer

G Sree Vidya 255 Reputation points Microsoft External Staff

2025-03-10T01:35:04.1133333+00:00

Hello Colin Gilchrist,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
G Sree Vidya 255 Reputation points Microsoft External Staff

2025-03-11T01:34:18.1866667+00:00

Hello Colin Gilchrist,

Following up to see if the below suggestion was helpful. And, if you have any further query do let us know.

Answer 1

Hello Colin Gilchrist

Greetings!

Could you please check the following details to verify the DNS resolver configurations?

Could you try performing an nslookup from the source machine and share a screenshot of the results?
Are you using Azure-provided DNS or a custom DNS in the Private Endpoint VNet?
If you are using a custom DNS, please let me know if the private endpoint and the custom DNS are in the same VNet. If they are in different VNets, you need to link the custom DNS VNet to the private DNS zone.
If you are using a custom DNS, please add the forwarder in the custom DNS server.
What is the PaaS service destination?

Please refer this document for more information.

Refer: https://github.com/msrini-MSFT/Troubleshooting-Private-Link-DNS-Scenarios?tab=readme-ov-file#scenario-2---if-your-source-machine-is-deployed-on-premises-other-cloud

Let me know if you have any further questions, we are happy to assist you.

Share via

The DNS service on my on-premise VM is not able to resolve the inbound endpoint in my DNS Private Resolver

1 answer

Your answer