Captive portal redirects to IP address not to a fqdn

If a guest user with an unmanaged device is redirected to authenticate against the captive portal,

the clients browser is pointed to the first IP address of the firewall.

Like URL]

The hostname or a configurable name should be used for the redirection to match with

a public trusted  certificate.

This is very important n environments were the accessing clients cannot be controlled

and the user should not be confronted with an certificate error.


Is there a plan to fix that? If yes, when?


Thanks, Friedrich