A quick followup to my previous post.
First, it's not needed to mess with ejabberd to see what Erlang resolver
configuration it sees -- it suffices to start the standalone Erlang
shell with the right parameters.
Second, this post [1] suggests to tweak the Erlang resolver config --
worth trying out.
How to do this.
1) As root, copy /etc/ejabberd/inetrc someplace (say, /tmp) and chown it
to the user you usually log in with.
2) Assumed the resulting file is /tmp/inetrc, and you have the
permission to read it, start the Erlang shell like this:
$ erl -kernel inetrc '"/tmp/inetrc"'
(notice the usage of quotes -- the Erlang itself must see "" around the
file name, so you have to protect them from the Unix shell).
3) At the Erlang shell's prompt, enter the commands mentioned in my
previous post:
inet:get_rc().
and
inet_res:getbyname("_xmpp-server._tcp.jabber.ru", srv).
4) Quit the Erlang shell, change the "nameserver" setting in
/etc/resolv.conf to "::1", restart the shell as shown above and retry
the commands.
5) Repeat steps (3) and (4) with
{inet6, true}.
added to the /tmp/inetrc so that it contents look like
{file, resolv, "/etc/resolv.conf"}.
{inet6, true}.
This setting is explained in [2].
In particular, it's interesting to know:
* Whether the resolving works for you on step (5).
* Whether the {inet6, true}. setting makes any difference.
1. http://erlang.org/pipermail/erlang-questions/2008-April/034230.html
2. http://erlang.org/doc/apps/erts/inet_cfg.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
