We have this very problem on

della — Tue, 01 Mar 2011 17:32:20 +0000

We have this very problem on our server now in production (Erlang R14A) after moving from an older machine, but we don't know Erlang. Can you help us in debugging the problem with detailed instructions?

thanks!
matteo

If you look at the error

mfoss — Sat, 25 Dec 2010 00:51:32 +0000

If you look at the error report, the DNS query is [<<"_xmpp-server">>,<<"_tcp">>,<<"die-informatiker">>,<<"eu">>,<<>>]

That <<>> at the end shouldn't be there. I tested a little with my ejabberd (Erlang R14B01 and R13B03), and couldn't reproduce your problem: all s2s works well in my server.

In an ejabberd live I tried:

ejabberd_s2s_out:get_addr_port("die-informatiker.eu").
[{"die-informatiker.eu",5269}]

In a simple erlang, I tried:

inet_res:getbyname("_xmpp-server._tcp.die-informatiker.eu",srv,10000).
{error,nxdomain}

You should check what changed in the ejabberd machine shortly before the problem was first reported: system upgrade, erlang upgrade, ...?. You can try to restart ejabberd.

If you find no clue, it would be possible to add some log lines to ejabberd_s2s_out.erl to see what exact calls to Erlang's inet_res does ejabberd perform in your server.

ejabberd - Comments for "Strange error for some hosts"

We have this very problem on

If you look at the error