Exchange 2010 CAS array without internal/external DNS
Posted on 2012-09-13
Hi y'all, this has been driving me crazy for days and I can't find good information on it anywhere.
How do I configure it so that my CAS array FQDN cannot be resolved externally while still allowing clients to resolve it internally? We have no hardware load balancer, we have no split DNS, we have no internal domain name, we have no ISA server. Basically, there is no "external" vs. "internal" aside from not being able to talk to domain controllers unless you're on one of our subnets.
Ultimately, what we need is something like the following
HUBCAS1 and HUBCAS2 configured in a NLB cluster
MBX1 and MBX2 configured in a DAG
OWA, Outlook Anywhere, Autodiscover, Activesync, etc. work no matter what network the client is on.
It works simply and straightforwardly in 2007, but this requirement to not have the CAS Array's FQDN resolvable externally is throwing me for a loop. If I don't put an entry in DNS, then clients on our subnets will not be able to find the CAS Array. If I put an entry in DNS, then clients not on our subnets will resolve the FQDN of the CAS Array and try to do a MAPI RPC connection. It's a catch-22.
Please, somebody set me straight! It can't be that complicated. Thanks in advance!