We have a customer, let's call them ABC123 Ltd, who have an existing website on abc123.ie hosted by a hosting provider. It's just an informational site with no login\commerce function so currently just runs over HTTP. They will continue with this.

They now want to implement a web application that must be hosted on-premises under IIS. They will be communicating with this web application using an Android app on tablets, via an domain name and port. The traffic for this must be over HTTPS.

The customer's premises has a static external IP.

So in overview abc123.ie is a website hosted by their hosting provider. They need to also have an on-premises web service secured by SSL.

My understanding of how this can be achieved is as follows.

  1. Customer obtains a new subdomain from the hosting provider, say mobile.abc123.ie.
  2. Customer generates a CSR on the on-premises server and obtains a domain-validated SSL cert from the hosting provider for mobile.abc123.ie.
  3. Hosting provider sets things up so that traffic for mobile.abc123.ie is forwarded to the external IP of the customer's premises.
  4. Customer's IT vendor configures on-premises firewalls for traffic on port 443 to be forwarded to the internal name or IP of the IIS server.
  5. We create a HTTPS binding for the web service in IIS and install the cert.
  6. Android devices hit https://mobile.abc123.ie to access the web service.

Does this sound sane?

1 Answer 1


Yes, this sounds like a normal way of doing things.

Step 3 will be via a DNS A record pointing mobile.abc123.ie to your external IP with the 443 port forward.

You could consider SSL offloading on your firewall if it is supported for increased performance and scale if that is a concern.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .