I'm required to implement a multisubnet availability group using SQL 2012 under the following requirements:
1. Legacy drivers that do not accept MultiSubnetFailover=TRUE
2. No DNS update from SQL Servers. DNS responds with multiple statically entered IPs for the listener.
(Added on 07/02/2015: Company policy prohibits database servers from dynamically updating DNS records, as in RegisterAllProvidersIP unfortunately does not help under this company policy.)
3. No streched VLAN. Geographically separated SQL on separate VLANs.
(Added on 07/02/2015: The current setup is a SQL Server 2012 SP2 availability group on multiple VLANs separated across multiple data centers. This works great for modern applications that can use MultiSubnetFailover=TRUE in connection parameter, but not so great for legacy applications.)
Could this be done in a way that legacy applications failover correctly?