Answered

On-prem Gateway

(1) Share

Report

Posted on by CG-04042015-0

Hello,

Trying to get the data gateway properly setup and after a lot of troubleshooting I found that the issue was our internal DNS with conditional forwarding to Azure DNS was the problem but I'm still not sure what domain is the problem.

I found this by switching my dns setting to use google dns and magically the Data Gateway can connect but when using the internal dns it won't work.

PS1: on the beginning (before using dns 8.8.8.8) the error when trying to register the gateway was "Failed to create gateway, try again", changing to 8.8.8.8 I was able to create

PS2: the error that I get in the Gateway application when using internal DNS after the sign in is "Failed to discover gateway collection"

Anybody know the list of conditional forwarders that should be setup in internal dns pointing to Azure DNS?

So far we have these in the conditional forwarders

analysis.windows.net
blob.core.windows.net
database.windows.net
dfs.core.windows.net
pbidedicated.windows.net
powerquery.microsoft.com
servicebus.windows.net
vault.azure.net
vaultcore.azure.net

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

HI @CG-04042015-0

Can you please explain it from the context of what you are trying to do. You are jumping into DNS, which this is not a DNS forum, without walking us through what you are doing as it relates to Power Platform, because PP would have no knowledge of your Internal DNS, so I am not sure what you are trying to do exactly and how you are trying to set it up end to end (not just the gateway) which would go in the Power BI forums.

Was this reply helpful? Yes No
CG-04042015-0 17 on at

Like (0)

Report
Copy link

Link copied!

I know this is not about DNS, but this is about Power Automate Gateway that is not working (I believe) because of some conditional Forwarding that need to be set.

The idea is to force all traffic between our network and azure network to go by the onprem-to-Azure VPN instead of using internet

we have sensitive data that cannot go to internet.

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @CG-04042015-0

The issue is, this isn't a Power Automate Gateway issue, its a network configuration issue.

The Gateway by itself isn't really the problem as in the end its still an On-Prem Gateway Product, not a Power Automate product.

Was this reply helpful? Yes No
Verified answer

CG-04042015-0 17 on at

Like (0)

Report
Copy link

Link copied!

Ok, I found the problem and it is resolved now...

The issue was with the conditional forwarder for analysis.windows.net which is necessary for power BI and Fabric, removing it the PBI and Fabric portal will stop working, but the Data Gateway will work

So, what I did is to configure in the server being used for gateway I created in the registry a persistent rule for DNS search that only affect to this server

this fixed my problem and the Data gateway is working without breaking the PBI and Fabric.

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @CG-04042015-0

I am glad you figured it out that it was in fact a DNS issue and were able to resolve it. The gateway itself is pretty simple so there isn't much too it.

Was this reply helpful? Yes No