Hi,
I am trying to sort out a SSL cert that will work with remote access for my home server.
I have purchased one from eNomCentral (Rapid SSL) who are holding the domain I am going to use. The cert has not been issued yet as I need to generate the CSR.
The DNS servers have been changed from eNomCentrals to the company I have a hosting package with. The subdomain I will use to connect to my come server is pointed (via a DNS alias record) to DynDNS which is kept sync'd to my regularly changing home IP address (no chance to change to static with any providers here without paying a big premium).
So, routes for;
Web and mail: eNom -> Hosting provider DNS -> Hosting Provider Servers.
Remote access: eNom -> Hosting provider DNS -> DynDNS -> Home server (running MS IIS7).
I need to use DynDNS as other services are filtered by corporate firewalls (homeserver.com for example).
The three questions I have are;
1. Will it work fine even through the funky routing.
2. Any gotchas to look out for / be aware of. Hate to get it issued and then find it doesn't work.
3. Do I need to issue it for rdp.mydomain.com (the subdomain matching the DNS alias) or mydomain.com (The purchased domain).
I would presume that the SSL Cert would not work with my hosting provider as they will be using a different web server but it would work with a website my home server runs if I redirected www (for example) to my home network.
Thanks
RB
I am trying to sort out a SSL cert that will work with remote access for my home server.
I have purchased one from eNomCentral (Rapid SSL) who are holding the domain I am going to use. The cert has not been issued yet as I need to generate the CSR.
The DNS servers have been changed from eNomCentrals to the company I have a hosting package with. The subdomain I will use to connect to my come server is pointed (via a DNS alias record) to DynDNS which is kept sync'd to my regularly changing home IP address (no chance to change to static with any providers here without paying a big premium).
So, routes for;
Web and mail: eNom -> Hosting provider DNS -> Hosting Provider Servers.
Remote access: eNom -> Hosting provider DNS -> DynDNS -> Home server (running MS IIS7).
I need to use DynDNS as other services are filtered by corporate firewalls (homeserver.com for example).
The three questions I have are;
1. Will it work fine even through the funky routing.
2. Any gotchas to look out for / be aware of. Hate to get it issued and then find it doesn't work.
3. Do I need to issue it for rdp.mydomain.com (the subdomain matching the DNS alias) or mydomain.com (The purchased domain).
I would presume that the SSL Cert would not work with my hosting provider as they will be using a different web server but it would work with a website my home server runs if I redirected www (for example) to my home network.
Thanks
RB