Openfire, when configured properly, is working purely based on DNS records. This is a two step process:
- To identify that DNS name of the servers that are running Openfire (you can have more than one, when running in a cluster), a DNS SRV lookup is done for the XMPP domain name. This results in DNS names for the server(s).
- For an individual server name, a DNS A (or AAAA) lookup is done, to find the IP address for that server.
(note that often, when not running in a cluster, the XMPP domain name will equal the DNS name of the server, which makes the DNS SRV lookup unneeded.
From what you’re describing, I’m guessing that you updated the DNS A records for your server, to point to the new IP address. If the network team sees that the “service is resetting”, but you can’t see that behavior on the server, then I’m wondering if the DNS changes have propagated successfully to all tools of the network team. I would not be surprised if some of the tools/checks check for the service on the old IP address, while others check on the new address. The reported result would be a “now it work, now it doesn’t” kind of deal.