I am runing ejabberd 2.0.1 and recently try to enabled s2s connection to receive messages from trop.im. My server seems to fail to establish proper s2s connection.
The ejabberd log and related s2s configuration are as follows. Please advise. Thank you.
From the log, it appears that the Jabber server at our end did get contact by jabber server at trop.im and try to establish the s2s connection by dialing back, but failed for some unknown reason.
-------- jabber log at our end -------------- =INFO REPORT==== 2011-11-19 11:25:35 ===
D(<0.583.0>:ejabberd_s2s_out:249) : s2s_out: connect return etimedout
=INFO REPORT==== 2011-11-19 11:25:35 ===
D(<0.583.0>:ejabberd_s2s_out:265) : s2s_out: inet6 connect return nxdomain
=INFO REPORT==== 2011-11-19 11:25:35 ===
I(<0.583.0>:ejabberd_s2s_out:224) : s2s connection: ourjabberserver.com -> tropo.im (remote server not found)
=INFO REPORT==== 2011-11-19 11:25:45 ===
I(<0.583.0>:ejabberd_s2s_out:777) : Reconnect delay expired: Will now retry to connect to tropo.im when needed.
=INFO REPORT==== 2011-11-19 11:25:45 ===
D(<0.583.0>:ejabberd_s2s_out:800) : terminated: {normal,wait_before_retry}
--- end of our jabber log --
--- our s2s jabber configuration ----
{s2s_use_starttls, true}.
{s2s_certfile, "C:\\Program Files\\ejabberd-2.0.1\\conf\\xxxxx.pem"}.
{s2s_default_policy, allow}.
--- end of related jabber config ----
I did some further testings,
I did some further testings, to help in understanding this problem.
I setup a jabber user registration at jabber.org, and use Spark IM client to send a message to my server. The message from this user account did get through from jabber.org server and showed up properly at my jabber server, with the above s2s connection setting.
But messages from trop.im are not getting through.
It appears that s2s connection to jabber.org server is fine, but not with tropo.im server. Why? Pls advise. Thank you.
This problem reported was due
This problem reported was due to DNS SRV resolution.
I found the link in http://www.ejabberd.im/fix-dns-srv and followed the suggestion Solution 3, adding the following to inetrc under /conf:
{nameserver, {208,67,222,222}}.
{nameserver, {208,67,220,220}}.
{registry, win32}.
On restarting, the DNS SRV resolution re s2s connection is resolved, and I can receive message from another server such as tropo.im
Thanks.