| T O P I C R E V I E W |
| MadCow |
Posted - 04/19/2012 : 09:42:58 AM
What would you name your CAS Array?
I see people using Outlook.domain.com??
Do we have to use the same name which we have specified on our NLB as the Full Internet Name or we can use the same VIP of the NLB and give it a different name in our internal DNS?
I am not sure what name to use? I was thinking of CASArray.domain.com????
Thank you |
| 5 L A T E S T R E P L I E S (Newest First) |
| clarinathan |
Posted - 04/20/2012 : 12:42:03 PM
LOL
Yes the point is that the CAS array name should not be resolvable in external DNS.
It should not be the same as the ExternalURL field used on the virtual directories such as OWA OAB etc.
This is because if you make things the same, there will be a delay whilst outlook externally tries to connect via RPC and then fails and falls back to HTTP.
One other thing, the CAS Array name doesn't need to be on the certificate on the Exchange server as it is an RPC endpoint not an HTTP endpoint.
Cheers
Nathan
|
| MadCow |
Posted - 04/19/2012 : 1:31:13 PM
Really?? |
| Jazzy |
Posted - 04/19/2012 : 1:08:04 PM
And you can also create a DNS record car.refrigurator.monkey.tree and point it to the same adress, then creat the CAS array with that name. :) |
| MadCow |
Posted - 04/19/2012 : 10:48:48 AM
Thanks Jazzy.
In my case the VIP Name is webmail.domain.com and it already has a IP in our internal DNS. So I should be using that same name for my CAS array name.
|
| Jazzy |
Posted - 04/19/2012 : 09:49:35 AM
The name you use for the CAS array is the name you use for the VIP. Your MAPI clients will try to connect to this name so you want them to connect to the VIP of your load balancer. And need of course a corresponding DNS record for this name pointing to the IP.
What name you choose doesn't matter, although best practice is not to use the same DNS name for internal MAPI and external Outlook Anyhwere connections. |
