iceshrimp.net - Link to source
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.
#xmpp #Jabber

Peter Vágner reshared this.

in reply to 🇨🇦Samuel Proulx🇨🇦

mastodon - Link to source

Matt Campbell

You can set up SRV records for your XMPP server, like this (in BIND format):

_jabber._tcp 300 IN SRV 0 0 5269 im.interfree.ca.
_xmpp-client._tcp 300 IN SRV 0 0 5222 im.interfree.ca.
_xmpp-server._tcp 300 IN SRV 0 0 5269 im.interfree.ca.

You'll probably also need to configure your XMPP server to handle the base domain.

in reply to 🇨🇦Samuel Proulx🇨🇦

snac - Link to source

Martin

There is no such thing as alias in #xmpp
fastfinge@im.interfree.ca is a different account than fastfinge@interfree.ca.
I think you can set up interfere.ca as another virtualhost and use migrate.modernxmpp.org/

XMPP Account Exporter

migrate.modernxmpp.org
in reply to Martin

mastodon - Link to source

Nicoco

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. :)

DNS configuration in Jabber/XMPP – Prosody IM

prosody.im
in reply to 🇨🇦Samuel Proulx🇨🇦

mastodon - Link to source

Zash

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 🇨🇦Samuel Proulx🇨🇦

mastodon - Link to source

Zash

Depends on what you mean by "interchangeably". The most popular XMPP servers support multiple Virtual Hosts, so you can add both. Accounts will be completely disconnected tho, which is what I meant by "not like email".
in reply to 🇨🇦Samuel Proulx🇨🇦

mastodon - Link to source

Zash

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.

@Prosody IM
This entry was edited (Friday, February 13, 2026, 4:04 PM)
in reply to 🇨🇦Samuel Proulx🇨🇦

friendica (DFRN) - Link to source

Peter Vágner

@🇨🇦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.
@Zash @🇨🇦Samuel Proulx🇨🇦
in reply to 🇨🇦Samuel Proulx🇨🇦

friendica (DFRN) - Link to source

Peter Vágner

@🇨🇦Samuel Proulx🇨🇦 #XMPP servers can import certificates from certbot. So if it's on a single machine I don't see this as a problem. If it's more complicated then you can setup DNS challenges while verifying certificate registrations. @Zash @0x0
#xmpp @Zash @🇨🇦Samuel Proulx🇨🇦 @0x0
in reply to Peter Vágner

iceshrimp.net - Link to source

🇨🇦Samuel Proulx🇨🇦

@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.
@Peter Vágner @Zash @0x0
⇧