Wildcards are only one level deep. So, if you had *.mycompany.com, that would cover www.mycompany.com<http://www.mycompany.com>, host.mycompany.com, etc.
But, it would not cover client.host.mycompany. Joe Heaton Enterprise Server Support CA Department of Fish and Wildlife 1807 13th Street, Suite 201 Sacramento, CA 95811 Desk: (916) 323-1284 From: David Lum [mailto:[email protected]] Sent: Thursday, April 11, 2013 2:22 PM To: Heaton, Joseph@Wildlife; NT System Admin Issues Subject: Wildcard cert Q If you have a wildcard SSL cert for *.mycompany.com would there be any reason to also have a *.host.mycompany.com SSL cert as well? Is there some scenario where this would be advisable? David Lum Sr. Systems Engineer // NWEATM Office 503.548.5229 // Cell (voice/text) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
