Observing DNS resolution failed when connecting to external application through RDP for .com url

PubSub+ Event Broker
, ,
1

We are currently using Solace 10.4.1.121 version deployed through Podman and observing this issue for many integrations whenever .com url is involved.

Flow : MuleSoft—>EMS(Solace RDP)—>MuleSoft(.com url) - Not working

But the same integration, when APIGW is involved in between it is working fine.

Flow : MuleSoft—>EMS(Solace RDP)—>APIGW—>MuleSoft(.com url) - Working

These traffics are going through Proxy and both EMS & APIGW backend servers have the Proxy configured and are able to connect to Proxy successfully.

Even through curl command we are able to get 200ok from the .com url in the EMS backend server. This tells us that there is no issue with the backend server however, on the application level Solace is unable to connect or recognize the proxy and the .com url.

We have also configured the Proxy under Message VPN of Solace broker and the same is being used in the RDP as well, still we observe the same error.

Kindly please let us know if anyone else has faced this issue and how this can be resolved.

2

Hi @Dhanusri ,

I know it’s been a few days, were you able to figure it out?

I would suggest checking what DNS servers are configured on Solace:

Hope that helps!

3

Hi @marc.dipasquale ,

We are currently using Solace Software Event Broker version 10.4.1.121 and we could observe the link you shared referes to appliances.

So, I believe the Solace broker would be using the same DNS as of the host on which it is deployed on.

Is my understanding correct ?

4

@Dhanusri I see it has been some time since you opened this thread but have you been able to solve the issue?
I am facing the same issue but for oauth-profiles. Using the http proxy in curl commands works fine but even if I am assigning that same proxy to the oauth profile, it shows that the “DNS resolution failed”.

5

Hey @Farouk,

We have recently upgraded our Solace PubSub+ Software Event brokers from version 10.4.1.121 to the latest version 10.11.1.147.

Post upgrading, we are able to connect successfully to the external systems hosted out of our org. network using the Proxy along with Oauth.

So, now we have excluded the APIGW layer in btw EMS & MuleSoft

Flow : MuleSoft—>EMS(Solace RDP)—>MuleSoft(.com url)

6

Hey @Dhanusri,

thanks for replying. Upgrading to 10.8.1.265 solved the issue for us also.