I have two servers; one is the 'official'
example.com server that hosts my public website as well as mail servers (bluehost.com). The second is my private LAN server which hosts my point of sale application and general 'manager' application.
example.com server has a wildcard SSL purchased and applied. I wish to use this certificate for all apps hosted on the private LAN server since it's a trusted certificate and it all apps mentioned are under the purview of the same company. I've read that this is simply a matter of copying the private and public key/cert files onto my server and configuring nginx to use them. I've done this but there is the issue that my current URL scheme (http://pos/ and http://manager/) won't end up matching the domain of the wildcard certificate.
The immediate solution would be to force all nginx LAN servers to use the longer URLs (like http://pos.example.com), however I'd like to avoid having to do that. Is there an elegant solution for this problem? The actual registered domain name takes a long time to type on mobile devices and it would just add a source of confusion for my employees using the pos/manager apps.
Would changing my LAN's connection-specific suffix to
example.com help in any way?