remote chatroom joining

Peter Saint-Andre stpeter at
Wed Nov 7 20:53:58 UTC 2007

Martin Atkins wrote:
> Clive Holloway wrote:
> [snip]
>> But I don't see a comment anywhere on how to deal with a service on a
>> remote host.
>> ie, if "" resolves through DNS, and "service" is running
>> on "", "" doesn't need to resolve
>> in DNS because it's actually "service" @ "", but that's
>> not how the DNS lookup is approaching it.
> I don't believe that the correct behavior is what you have described.
> and service at are two distinct JIDs.
> If JIDs in are to be accessible by S2S, then a
> SRV record must be published for

You don't want to do that because is not an XMPP
server that listens on port 5269, it is an add-on service hosted by the
XMPP server at (which handles the server-to-server traffic
for all subdomains at

However, you may want to resolve, since the
resolutions might be used in server dialback (and could be used in TLS
and SASL too).

> or alternatively, you could publish a record like:
> assuming you already have the relevant A record published for
> and you're using the standard S2S port.

Typically if you want users from foreign domains to access your add-on
service then you would publish a DNS record like this (the example is
from the DNS setup, where we have a MUC service called

conference   IN A


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url :

More information about the Djabberd mailing list