Accessing internal web server when SSL other than 443

[wildfrog]

I have a server on the LAN that's managed via a web browser. It uses port 8443 for SSL and not 443.
I have a port forward sending incoming 443 traffic to port 8443 of that server.
I have a host override in DNS Resolver sending the FQDN to the internal IP.
From outside the office, all works properly. I can manage the server. SSL works.
From inside the office, going to https://server.domain.com does not resolve.
However, inside the office, I can go to https://server.domain.com:8443 and that comes up as expected.

I'm sort of at a loss on how to reach the server via SSL the same way whether inside or outside the office.
I have tried using NAT reflection, both as Pure NAT and NAT+proxy, with no success.

Is there anywhere else I should be looking?

[johnpoz]

"From inside the office, going to https://server.domain.com does not resolve."

Yes it does resolve or server.domain.com:8443 wouldn't work either..  If your service is listening on 8443 then yes you would have to tell your browser to go to that port, not just resolve the fqdn to your internal IP.. dns has zero to do with ports.

Simple solution - save a bookmark in your browser to the 8443 url ;)  Other solution be to just do a nat reflection, or setup an internal port forward.

Or change this server to listen on 443 ;)  Or setup the server to redirect traffic it sees on 443 to the application on 8443..