Hey #xmpp and #jabber experts on Mastodon: my XMPP server is im.interfree.ca, and so my JID is fastfinge@im.interfree.ca. However, I would like to alias my JID to fastfinge@interfree.ca. That way my email, jabber, and fediverse id's are all the same. I control the DNS on the entire domain. How can I do this? A quick search isn't finding me a list of clear and straightforward steps.

Peter Vágner reshared this.

in reply to 🇨🇦Samuel Proulx🇨🇦
in reply to Martin
They are different accounts indeed, but I think what you are looking for is DNS SRV entries. prosody.im/doc/dns explains it better than I would. Also, do not hesitate to ask in the support room of your xmpp server directly. As expected, people developing xmpp servers are usually available for support on xmpp. :)
in reply to 🇨🇦Samuel Proulx🇨🇦
As others already pointed out, you can do it with SRV records. As a bit of expectation management, be aware that XMPP is stricter with routing so there isn't really the kind of aliasing you may be familiar with from email. If you already have contacts with that JID then those will stop working if you rename your host.
in reply to Zash
@zash Yeah, that's not what I want. I want to use the same username and password to get messages for fastfinge@interfree.ca and fastfinge@im.interfree.ca. I had to run xmpp on a subdomain because my primary domain runs other services.
in reply to 🇨🇦Samuel Proulx🇨🇦

Then I'm afraid you will be disappointed. Sorry.

At least in @prosodyim we made `prosodyctl check config` try to steer users away from such names, since it is really hard to change afterwards.

This entry was edited (Friday, February 13, 2026, 4:04 PM)
in reply to 🇨🇦Samuel Proulx🇨🇦
@🇨🇦Samuel Proulx🇨🇦 You may be missunderstanding @Zash I'm afraid.
The server host name does not have to match your virtual host. So you are fine hosting domain interfree.ca on im.interfree.ca .
What is not possible is redirecting or forwarding existing subscriptions from fastfinge@im.interfree.ca to fastfinge@interfree.ca.
Thus you can add two accounts into your clients during transition period if you are okay with that.
in reply to Peter Vágner
@pvagner@zash@0x0 The issue is I have apps that require certificates in different formats. And I'd rather not store unencrypted privkeys on disc somewhere to convert from one format to another. And set up chron jobs to get the conversion done every time a certificate renews. And I issue a wildcard cert for most things. But XMPP servers don't seem to support wildcard certs. Sharing certs between apps is a giant mess; it's fine for HTTPS, because you just reverse proxy everything. But IRC and SMTP and IMAP and XMPP all have different requirements. What we need is a certificate manager that all apps use, that manages what apps have permission to use what certificates, tracks what's using what, handles renewals, and keeps the three different formats for storing certificates in sync. And then we need all apps to use it.