The relevant section in resolver.xml is:
<lookup>
<!-- _xmpp-server._tcp is mandated by the XMPP spec -->
<srv>_xmpp-server._tcp</srv>
<!-- traditionally, _jabber._tcp has been used -->
<srv>_jabber._tcp</srv>
</lookup>
That is the default - I haven't changed it. Is that right?
Thanks for the help, and my apologies for the slow response.
~Craig
On Mon, November 12, 2007 10:00 am, Tomasz Sterna wrote:
> Dnia 11-11-2007, nie o godzinie 00:56 -0500, Craig Andrews pisze:
>
>> Jabberd2 should have connected to xmpp-server.l.google.com with IP
>> 209.85.163.125.
>>
>
> This is a bit strange.
> Do you have <lookup/> section in s2s.xml configured correctly?
>
>
>
>> Is there something wrong with Jabberd2's resolver?
>>
>
> Well... ;-)
> Depends on how you look at it. It generally works, but...
>
>
> It does not use alternative addresses - only the first one.
> It does not honor SRV records weight.
> There are problems with synchronous resolution timeouts.
>
>
> Enough to say, it's currently under major rewrite and should work better
> with next release.
>
>
> --
> /\_./o__ Tomasz Sterna
> (/^/(_^^' Xiaoka.com
> ._.(_.)_ XMPP: [EMAIL PROTECTED]
>
>
> _______________________________________________
> Jabberd2 mailing list
> Jabberd2@lists.xiaoka.com
> http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
>
>
_______________________________________________
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
