I don't think you need to name the server "chat". But i haven't done this, so i'm only assuming. You can create a DNS entry (alias: pointing chat.contoso.com to servername (if the server's name is already resolvable by some other DNS record), or a record: pointing chat.contoso.com to IP address of the server). Then you can create a SRV record pointing queries to conto.com on 5222 to chat.contoso.com. This should get rid of a warning. Though, that warning is more like informational and things can work correctly even with it showing (in some cases, like in mine). Your fqdn can even be just chat. I don't think there is a requirement for it to replicate the main domain name. XMPP doesn't understand subdomaining. chat.contoso.com and contoso.com are two completely different domains for XMPP. Your users would need to put conto.com in their clients for login, so chat.contoso.com is not anywhere in that scheme.
I would try:
name server - chatserver
put chatserver as fqdn during setup
put conto.com as xmpp domain during setup
add A record pointing chatserver to its IP
add SRV record for queries to conto.com on 5222 to point to chatserver
It kept asking me to complete the setup because I forgot to restart openfire after moving the config files
Ok, I had everything running. I could even login to the new server (using IP instead of server name), but as soon as I swapped the IP address I was not able to login anymore.
The old server has multiple Virtual NICs, so maybe something is configure thru a different IP? I checked and everything seems to be configured thru server name, or localhost. So not sure.
For the moment, I swap it back (using old server for the weekend) but the new server does not work anymore. Weird.
I also made sure routing is right (I did have 1 problem there before, but it is fixed now)
I think I kind of found the problem and I might have to start from scratch since it has been so long.
But is there a way to re-launch the setup tool?
Also, it seems I when I copied the data I overwrote the MSQL connection, and it has different versions.
Also, how can I reencode the username and password?
OK, from openfire.xml I changed the values and removed the encrypted directive. After restarting OF it encrypted it.
Are there also DB settings saved somewhere else?
To restart the setup edit the openfire.xml and change the last <setup> tag to false. Almost all the settings (except for DB connection string) are saved in the database. It then removed that data from the openfire.xml file.
I took notes in all the changes to make it easier in the next migration.
I think I had a connection, and password issue, plus networking routing issue in my first try (the networking is due to my lack of experience in Linux Static IP )
What I ended up doing is running a clean install, then deleting the very few tables that had data besides property and then move everything over from the original DB.
After I did however I noticed that new Openfire version also encrypts the AD connection account as well. I think I might not have changed one of the accounts in the DB when I did the move the first time too
Life learning lesssons
Do you think there will be any issues with the aproach I took?
Spark and imessage clients connected with no problem. However my Xabber (the client I use from my Android phone) cannot connect
It's hard to follow the things you do. And i don't know why you do this. It seems that you are trying to migrate your server to a new one. But why do you have to take parts of one database and replace parts in another one i don't understand. Xabber issue might not be related. Not sure if Xabber has any logs to clarify the issue.