> I assume the server is going to be run under xmpp.example.com and you all the following domains have been set up. > [multiple A records] "A" DNS records may

> I assume the server is going to be run under xmpp.example.com and you all the following domains have been set up. > [multiple A records] "A" DNS records may be used for a fallback, but SRV records are the primary way to configure those [1, 2]. Also some of those can reuse an existing domain name, and some may not have any DNS RRs, but only be used as an internal JID. > ejabberd is a robust server software, that is included in most Linux distributions. Prosody [3] is another nice and popular option. > Install from Process One repository > Install from Github Both ejabberd and Prosody are available from regular Debian repositories as well. > Make sure the fowolling ports are opened in your firewall, taken from ejabberd firewall settings. A port range is also needed for TURN, to use for relaying. And there is a typo. > Clients I can recommend are Profanity, an easy to use command-line client, and Monal for MacOS and iOS. Among relatively feature-rich and user-friendly ones (quite polished, supporting more recent standards, including voice calls with DTLS-SRTP, OMEMO), there are also Conversations for Android, Dino for Lignux (GUI), poezio for TUI (though that one has no voice calls). Setting converse.js (a Web client) may also be convenient (and done rather easily, at least with Prosody). [1] https://www.rfc-editor.org/rfc/rfc6120.html#section-3.2.1 https://www.rfc-editor.org/rfc/rfc6120.html#section-3.2.1 [2] https://xmpp.org/extensions/xep-0368.html https://xmpp.org/extensions/xep-0368.html [3] https://prosody.im/ https://prosody.im/