[jadmin] Jabberd-2.0.11 DNS issues

[Maxim Britov]

> our small Jabberd2 server has an issue resolving _xmpp-server._tcp SRV
> DNS entries for servers which don't listen for s2s connections on the
> IP provided by the "A" DNS entry. Such servers are for example:
> "jabber.ccc.de", "amessage.de". Instead of using the correct SRV DNS,
> the resolver module returns the "A" entry which of course makes it
> impossible for s2s to establish a connection:
> 
> jabberd/s2s[15790]: [25] [208.245.212.98, port=5269] outgoing connection
> jabberd/s2s[15790]: [25] [208.245.212.98, port=5269] write error:
> Connection refused (111)
> jabberd/s2s[15790]: [25] [208.245.212.98, port=5269] disconnect

For my jabberd2 (s2s) for amessage.de:
Wed Nov  8 09:55:12 2006 [notice] [13] [212.112.238.55, port=5266] outgoing connection
Wed Nov  8 09:55:13 2006 [notice] [13] [212.112.238.55, port=5266] sending dialback auth request for route 'modum.by/amessage.de'
Wed Nov  8 09:55:13 2006 [notice] [17] [212.112.238.55, port=39641] incoming connection
Wed Nov  8 09:55:13 2006 [notice] [17] [212.112.238.55, port=39641] incoming stream online (id z58hens9xaj5fcpld6bbbrk03fxgtl4trca503ey)
Wed Nov  8 09:55:14 2006 [notice] [17] [212.112.238.55, port=39641] incoming stream online (id ey3ubsfozr0aikbm092tv7mmjxsk07jf5n9gfo4e)
Wed Nov  8 09:55:14 2006 [notice] [17] [212.112.238.55, port=39641] checking dialback verification from amessage.de: sending valid
Wed Nov  8 09:55:14 2006 [notice] [13] [212.112.238.55, port=5266] outgoing route 'modum.by/amessage.de' is now valid, SSL negotiated
Wed Nov  8 09:55:14 2006 [notice] [23] [212.112.238.55, port=39642] incoming connection
Wed Nov  8 09:55:14 2006 [notice] [23] [212.112.238.55, port=39642] incoming stream online (id f4pyp0lp9nj4v6rf3jz4qjjv6scmhh1xlqvbqg10)
Wed Nov  8 09:55:14 2006 [notice] [23] [212.112.238.55, port=39642] incoming stream online (id 4k50rwfuffy6yi24aeqsvrphilt82u97fe76am1q)
Wed Nov  8 09:55:14 2006 [notice] [23] [212.112.238.55, port=39642] received dialback auth request for route 'modum.by/amessage.de'
Wed Nov  8 09:55:15 2006 [notice] [23] [212.112.238.55, port=39642] incoming route 'modum.by/amessage.de' is now valid, SSL negotiated

Resolver:
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5262 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5267 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5264 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5265 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5260 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5261 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5263 (3600 seconds to live)
Wed Nov  8 09:55:12 2006 [notice] [_xmpp-server._tcp.amessage.de] resolved to 212.112.238.55:5266 (3600 seconds to live)


-- 
Maxim Britov

GnuPG KeyID 0x4580A6D66F3DB1FB xmpp:maxim at modum.by icq 198171258
Fingerprint: 4059 B5C5 8985 5A47 8F5A 8623 4580 A6D6 6F3D B1FB
GnuPG-ru Team (http://lists.gnupg.org/mailman/listinfo/gnupg-ru
               xmpp:gnupg-ru at conference.jabber.ru)