Tenant SQL Servers - Support for Split Domain Models
The resource provider for SQL Server is pretty screwed when it comes to supporting controlling resources in a child domain or partially trusted remote forest. The specific issue I have is in my test environment:
HarmfulHosting.net - The Domain where everything lives.
HarmfullyHosted.net - Tenant resources
When you add a SQL Server AlwaysOn resource to the SQL Server resource pack, it queries the list of replicas for the SQL Server via the DMV's (sys.availability_replicas) to find who to put the databases on-to.
The trouble is that whilst it's smart enough to take the FQDN end-piece off when adding the AG name (an old WAP version didn't do this, so you couldn't add the AG at all if it wasn't on the same parent domain) - it's not smart enough to put it back on when connecting to the nodes.
HARMWAPAAPI01 - Admin API Server 01 in my farm, when adding HARMAG-TENSQL.harmfullyhosted.net (My Tenant SQL Server AlwaysOn listener) will connect to the primary of the availability group. It will then query for replicas of 'HARMAG-TENSQL' - note it's dropping the FDQN.
However then it gets the node names back: HARMTENSQL01/HARMTENSQL02 - which will then attempt to be connected to from the Admin API box directly - from the administrative/non-tenant domain.
The 'workaround' here is to add DNS dummy records in my management domain for the individual server nodes in the Availability Group, so a non-FDQN DNS lookup in the domain will succeed - and find the IP addresses.
Please fix this.