topic Re: Set UserCheck URL via API fails DNS check in API / CLI Discussion

Set UserCheck URL via API fails DNS check

Harald_Hansen — Wed, 21 Sep 2022 16:08:40 GMT

When running:

set-simple-gateway usercheck-portal-settings.portal-web-settings.main-url "https://hostname.tld/UserCheck"

the command fails with generic_error and "DNS failed to resolve the hostname: hostname.tld."

I've checked with tcpdump and the SmartCenter is resolving this name correctly.

Setting the Main URL field via SmartConsole succeeds.

Setting other hostnames, like www.cnn.com, work.

I use hostname.tld on multiple gateways, as all of them are contained behind the same load balancer in Azure.

api.elg and cpm.elg confirm the issue is related to gateway_legacy.portals_manager.PortalRequestsValidationHelper.

Anyone seen something similar?

The goal is to set a name and certificate for UserCheck in Azure Scale Set gateways.

Re: Set UserCheck URL via API fails DNS check

PhoneBoy — Fri, 23 Sep 2022 16:36:02 GMT

@Omer_Kleinstern what say you?

Re: Set UserCheck URL via API fails DNS check

_Val_ — Mon, 26 Sep 2022 06:34:47 GMT

Do you run the command on your SMS or on another machine? If the former, please take this with TAC. If the latter, you may need to set up the name on the client as well.

Re: Set UserCheck URL via API fails DNS check

Harald_Hansen — Mon, 26 Sep 2022 11:18:58 GMT

This script is to be run as part of CME, so it is only run on the SMS.

Re: Set UserCheck URL via API fails DNS check

_Val_ — Mon, 26 Sep 2022 11:59:05 GMT

Understood, please take this with TAC

Re: Set UserCheck URL via API fails DNS check

bernhard_m — Mon, 02 Oct 2023 10:05:34 GMT

Have you been able to find a solution for this? I've got the same issue.

Re: Set UserCheck URL via API fails DNS check

Harald_Hansen — Mon, 02 Oct 2023 10:54:08 GMT

Hi,

No, I gave up on this.

Can confirm the issue still persists on R81.20 in my lab.

Best regards,
Harald

Re: Set UserCheck URL via API fails DNS check

bernhard_m — Tue, 10 Oct 2023 09:09:31 GMT

I opened a case for it and got the information that a Hotfix is available on request and that the fix will be integrated in a future Jumbo (PRHF-28814, PMTR-91949).

kr, Bernhard