> 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
>
> I suppose that it's not the nameserver's fault, as the
dig command returns
> the proper _xmpp-server entries: "dig
_xmpp-server._tcp.amessage.de SRV"
>
> Meanwhile I've used the quick & ugly method of
redirecting the
> corresponding IPs via iptables which is a really dirty
solution.
> Can anyone report similar problems with Jabberd2?
Yes, this happens on our server, too. Actually, your post
finally made me
look in the right direction  Anyway, on
our server, connections to
jabber.ccc.de fail as well as connections to gmail.com -
same problem,
both services report different IP addresses for
_xmpp-server._tcp than
for simple A records.
Could you post your quick-and-dirty fix, perhaps?
In the long run, this should be solved in the code, of
course, as it's
obviously a bug. I'll try to come up with a patch.
Florian
_______________________________________________
JAdmin mailing list
JAdmin jabber.org
http:/
/mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://ww
w.jabber.org/about/jadminfaq.shtml
_______________________________________________
|