[ejabberd] Ejabberd clustering

Jacek Konieczny jajcus at bnet.pl
Tue Jan 25 10:49:45 MSK 2005


On Mon, Jan 24, 2005 at 08:09:05PM +0300, Oleg V. Motienko wrote:
> Can anybody publish an example of DNS configuration with fallback server 
> or point me to a documentation file?

http://www.ietf.org/rfc/rfc2782.txt

Example: assuming the Jabber server name is "example.com", the
primary servers are: a.example.com (10.0.0.1) and b.example.com
(10.0.0.2), and the backup server i backup.example.com (10.0.0.3); all
the servers accepts both client and server connections (this may be
split between different machines) on standard ports (5222 and 5269); the
servers provide MUC service available from outside as "muc.example.com"

$ORIGIN example.com
_xmpp-client._tcp	IN	SRV	10 0 5222 a.example.com.
_xmpp-client._tcp	IN	SRV	10 0 5222 b.example.com.
_xmpp-client._tcp	IN	SRV	20 0 5222 c.example.com.
_xmpp-server._tcp	IN	SRV	10 0 5269 a.example.com.
_xmpp-server._tcp	IN	SRV	10 0 5269 b.example.com.
_xmpp-server._tcp	IN	SRV	20 0 5269 c.example.com.
_xmpp-server._tcp.muc	IN	CNAME	_xmpp-server._tcp
a.example.com		IN	A	10.0.0.1
b.example.com		IN	A	10.0.0.2
c.example.com		IN	A	10.0.0.3


> What other jabber server software have proper SRV records support? 

I guess nearly every server implementation supports SRV records now.

> What 
> I must to do to save compatibility with old server versions (IN A record 
> and open 5269/tcp I guess) ?

I would not bother with compatibility with servers not supporting SRV at
all. Those are pre jabberd-1.4.x and not usefull today anyway.

Bigger problem are misconfigured servers (e.g. <= jabberd-1.4.3 with default
configuration) wich resolve only the legacy _jabber._tcp SRV record.
For such servers you would also need the old SRV record:

_jabber._tcp		IN	SRV	10 0 5269 a.example.com.

Greets,
	Jacek


More information about the ejabberd mailing list