Link to home
Start Free TrialLog in
Avatar of unrealone1
unrealone1Flag for United Kingdom of Great Britain and Northern Ireland

asked on

.local SSL certs


I have a client that has an onsite exchange server which the clients connect up to. So for example ctfserver.cfuture.local is the local address it is sitting on for the client machine, also sitting on this same .local address.

Is there a way round this? I have heard that SSL cert providers don't offer them for .local addresses anymore. Is it possible to change the server address to resolve from IP either internal or external IP for the exchange server?


Avatar of M A
Flag of United States of America image

Add only 2 names which is common name and make both internal and external the same. Please check this
Avatar of Jason Crawford
Jason Crawford
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of unrealone1


Keyser Soze,

Thank you for your input. I am running Exchange 2010.

Avatar of Jody Whitlock
Jody Whitlock

Honestly for any internal systems, I would create an Enterprise CA on your domain controller and have the servers auto-enroll that way so you would have .local SSL Certificates available to your internal clients and have your traffic secured.  
When you create the Enterprise CA, it get's published in AD and added to domain members automagically.