[ejabberd] no more s2s connections possible

Wijnand Wiersma wijnand at nedbsd.nl
Sun Jun 10 17:12:01 MSD 2007


Op 10-jun-2007, om 3:51 heeft Evgeniy Khramtsov het volgende geschreven:

> Wijnand Wiersma пишет:
>
>> Hi,
>>
>> since today (or maybe earlier) my server does not get any s2s
>> connections anymore.
>> Does anyone know if I am hitting some sort of bug or how I can debug
>> this with ejabberd?
>> Telnetting to port 5269 works and I can reach other servers on port
>> 5269. There have been no DNS changes and the ip stayed the same.
>>
>> I hope somebody can help me out, this is a huge problem.
>>
>> Wijnand
>>
> Your SRV record is invalid:
>
> $ host -t srv _xmpp-server._tcp.nedbsd.nl
> _xmpp-server._tcp.nedbsd.nl SRV 0 5269 5 jabber.nedbsd.nl.
>
> Jabber servers are trying to get your server on port 5, not 5269 :)

So, what you are saying is someone made a booboo on http:// 
jabberd.jabberstudio.org/2/docs/section05.html#5_7 ?

Bind example:
         _jabber._tcp.some_domain.com. 86400 IN SRV 5 0 5269  
host.some_domain.com.
         _xmpp-server._tcp.some_domain.com. 86400 IN SRV 5 0 5269  
host.some_domain.com.
         _xmpp-client._tcp.some_domain.com. 86400 IN SRV 5 0 5222  
host.some_domain.com.

on my bind server:
_jabber._tcp   IN      SRV     5 0 5269 jabber.nedbsd.nl.
_xmpp-server._tcp IN SRV 5 0 5269 jabber.nedbsd.nl.
_xmpp-client._tcp IN SRV 5 0 5222 jabber.nedbsd.nl.

for each domain I am serving and that has been working for years.

Wijnand


More information about the ejabberd mailing list