Some ansers posted in the Mid-Tier Forum:  Hi Dexter.  Please define “some nodes”. Are you talking client nodes? DNS servers? Consider that clients *never* talk to the SSIP directly. They make a DNS lookup to the DNS server and the DNS server talks to the cluster.    Anyway, I was talking to Andy about this yesterday. If you want the DNS servers to use a single SSIP for multiple SC zones, normally you would need an extra level in the naming e.g.     If the clients are in “isilon.com” and you don’t want them to have to deal with the extra level of indirection, you’d then create individual CNAMEs in isilon.com viz:zone1.isilon.com CNAME zone1.mycluster.isilon.com  …    Back to the current question. As I mentioned at the start, only the DNS server talks to the SSIP. It doesn’t matter if it’s handing out addresses for multiple subnet:pools for clients in different VLANs, since the clients aren’t talking to the SSIP, the DNS servers are and the clients are talking to the DNS servers. So the only routing that matters wrt the SSIP is whether the DNS servers can talk to it.    Does that all make sense?   Have you explored using DNS CNAMEs and potentially SmartConnect zone aliases yet?    You can create a single delegation zone, 1.isilon.com and then use CNAMEs to point 2.isilon.com -> 1.isilon.com and 3.isilon.com -> 1.isilon.com    If you need to have the cluster actually register the names with AD as services, you can use SmartConnect Zone aliases.  So you create 1.isilon.com and then on the cluster you create the aliases 2.isilon.com and 3.isilon.com in the same Subnet/pool as 1.isilon.com    Is this getting more toward what you want to achieve?  A more detailed example would be helpful.
IHAC that I just spent some time setting up SmartConnect and AccessZones with. One of the challenges that we came up with is that I can’t seem to get multiple DNS delegates associated to multiple SmartConnect Pools/Zones to point to the same SmartConnect Service IP.  So what we want is:   What I can get but don’t want is:    But that is not optimal for the use case. They want to ensure that when somebody pings “1”  they don’t see the full path. ACLs and permissions are setup to ensure security but the challenge is eliminating even the knowledge. Is this possible or would I have to implement multiple subnets?
Multiple DNS Delegates Pointed to Single SIP