iamuser
asked on
Cass array on San certificate
Is the name of the Cass array on the SAN supposed to be the internal name or an external name? and if it is the external name does that mean we have to add the Cass to our external DNS?
ASKER
This is the logical name, the issue is that my internal is different to my external. All the examples I've seen are always cas.domain.com
For us though our internal is inside.domain.com. The internal dns will have the array as array.inside.domain.com
So I don't see how array.domain.com is going to resolve to array.inside.domain.com. Or even how this certificate is going to be valid as both fqdn are different
For us though our internal is inside.domain.com. The internal dns will have the array as array.inside.domain.com
So I don't see how array.domain.com is going to resolve to array.inside.domain.com. Or even how this certificate is going to be valid as both fqdn are different
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is the logical name\object for few CAS servers correct?
We need to have this name visible for both the Internal and External Users\access.
>> On the MBX databases we need to add the same CAS-array name
>> The traffic from the external world (eg. OWA) should reach the CAS-array-name to get the OWA requests completed\fulfilled
Or AM i missing something here in the question