It's not uncommon to have a url that you want people to use that doesn't match the actual machine name. Whether it's because you need to make sure people use or don't use an FQDN (server vs server.example.com) or because you want to use a friendly dns alias instead of the ugly name IT gave the machine, or you're in a cluster scenario and users should never see the name of either machine. This goes double for https, since the url has to match the certificate. In those cases, you need to tell the application how to build the url instead of letting it guess.