Havin trouble with gtalk users again.. :-/

This is weird but after I upgraded jabberd2 my users are again
experiencing issues with google gtalk users and only with them..
log:

 fgrep \'binaryfreedom.info/gmail.com\' /var/log/jabber/s2s.log |tail -4
Sat Feb 21 19:46:00 2009 [notice] [24] [209.85.162.129, port=55426]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'
Sat Feb 21 19:48:57 2009 [notice] [24] [209.85.162.129, port=55426]
dialback for incoming route 'binaryfreedom.info/gmail.com' timed out
Sat Feb 21 19:48:59 2009 [notice] [24] [209.85.162.129, port=56412]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'
Sat Feb 21 19:49:26 2009 [notice] [68] [209.85.162.129, port=56551]
received dialback authrequest for route 'binaryfreedom.info/gmail.com'


the last time I fixed this  by adding the right lookout info on
s2s.xml... I have not touch it since them, here is what I have:

<lookup>
     <!-- SRV TCP services will be resolved in the following order. The
first
          one that returns something will be used (ie dereferenced via an
          A/AAAA lookup). If no SRV records are found, resolver will
          fallback to a straight A/AAAA lookup. -->

    <!-- xmpp-server is mandated by the XMPP spec -->
    <srv>xmpp-server</srv>

    <!-- traditionally, jabber has been used -->
    <!-- <srv>jabber</srv> -->


    <!-- If this is enabled, the resolver will look up AAAA records as well
         as A records. This is needed if you want s2s to use IPv6.
         Connection attempts will be made to all IPv6 hosts before trying
         IPv4 (see bad host timeout below). -->
    <!--
    <resolve-ipv6/>
    -->

    <!-- Minimum time that DNS lookup results are cached (overrides max
below). -->
    <min-ttl>30</min-ttl>

    <!-- Maximum time that DNS lookup results are cached. -->
    <max-ttl>86400</max-ttl>

    <!-- Minimum time to wait before using hosts that we have failed to
         establish a connection to (unless there are no alternatives).
<!-- Maximum time that DNS lookup results are cached. -->
    <max-ttl>86400</max-ttl>

    <!-- Minimum time to wait before using hosts that we have failed to
         establish a connection to (unless there are no alternatives).
         Do not set this too low - it is required to detect permanent
         problems like broken IPv6 connectivity in order to attempt IPv4.

         0 disables bad host caching.               (default: 3600) -->
    <bad-host-timeout>3600</bad-host-timeout>

    <!-- Disable the DNS cache (negative caching will still be done).
         This is likely to negatively impact performance while saving
         a small amount of memory since multiple DNS requests must
         then be made for every re-connection. -->
    <!--
    <no-cache/>
    -->
  </lookup>


Any ideas? someone else experiencing this issues?

Im running Gentoo(updated) and compiled jabberd2 with this USE flags
net-im/jabberd2-2.2.5  USE="berkdb mysql pam ssl zlib -debug -ldap
-memdebug -postgres -sqlite" 0 kB

Thanks
_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: [email protected]
_______________________________________________