Well, i would understand such setup if users were to be isolated (one location from another). Now you have to deal with s2s setup for them to be able to talk to each other. Of course, when one location goes down, then the other part still can talk among each other. But that would be solved by some failover (cluster for database and cluster for Openfire). Clustering could be more complex though.
Anyway. Do you have any problems with Openfire or s2s connection between servers? A warning about SRV records on admin page is only an informational thing. It might be working ok depending on your setup. It just informs you that you may make it more proper by adding SRV records.
Though in your case i wonder if it is even possible to have such records. Because SRV record is to point a client which is looking for any xmpp server on your domain to a particular server/machine. In your case there are two servers in your domain, so SRV record won’t help\work i think. SRV record’s format is like
xmpp-client.tcp.example.com IN SRV 0 0 5222 jabber.example.com.
This points a querying client (looking for a xmpp server on example.com) to jabber.example.com server. So, if you would have two SRV records pointing to two different servers, i think in some cases clients would be trying to connect to a wrong server. Also, in this example a client is trying to connect to a domain, not to a particular server or IP address. SRV records are only useful in such case.
If it doesn’t work now, then what was your setup before? What were servers’ names, how were users logging into their clients (domain/server part) on both locations? I assume they were using different server names/IP addresses .