Thanks, @ZackButcher. I have seen this description but thought that it perhaps did not apply to the split-horizon EDS deployment method since the config push should mean that the proxy sidecar of the application would know to resolve someservice.remote.svc.cluster.local to the configured gateway of that cluster which would then use SNI to direct the traffic.
I’ve just taken a look at our cluster and I see no CoreDNS service was created as part of the chart installation of Istio in the cluster-aware routing, split-horizon EDS pattern. For the record, this style of resolution works correctly from within the Istio master cluster but not from the remotes. That is, the cluster containing the full Istio control plane can resolve someservice.remote.svc.cluster.local just fine but an application in say, remote2 cannot do so.
EDIT: I apologize, I updated this much older ticket in error. I think the newer issue I have created is more clear on what we are aiming for and what is not working: Cross-Cluster DNS Resolution in Split-horizon EDS Not Working