Quote:
Originally Posted by rayt_rwm We are going to use the server primarily as an Internal domain mail server. I want to get the https sessions to work, but I don't want to lose the performance on the internal domain. We cannot be the only company with an internal domain (that was setup 15 years ago) that is different from their FQDN. |
The FQDN doesn't actually have to be the same as your 'real' domain although to save confusion I'd usually recommend that it is.
Quote:
Originally Posted by rayt_rwm Maybe I could give it a FQDN, and tell our Internal DNS to point it at the Internal IP, and when they use the internet from "outside" the Firewall will still point traffic correctly. If that doesn't work I will be looking at an ssl-vpn to use instead. |
If you wish to use the server just to send internal mail only then search the wiki for the word 'restrict'.