Forum Discussion
Oct 16, 2018
Hey sysadmin_2015
The reason why the browser does not change the URL is because you are simply rewriting the HTTP::header on the server-side connection. The IIS will accept the traffic because IIS Binding is receiving the correct HTTP header.
In order to have the web browser change the URL, you will need to redirect the user to the correct URL. However, based on the question, I'm guessing the FQDN is not resolvable by the client. Is it a Client VPN or a Site-to-Site VPN? If it's a Client VPN you could change the DNS servers of the client to one that can resolve the FQDN.