[ejabberd] s2s conf issues
stpeter at jabber.org
Tue Mar 8 02:12:23 MSK 2005
On Tue, Mar 08, 2005 at 12:06:48AM +0100, Andreas van Cranenburgh wrote:
> On Mon, Mar 07, 2005 at 05:05:06PM -0600, Peter Saint-Andre wrote:
> > On Mon, Mar 07, 2005 at 04:23:20PM -0600, Peter Saint-Andre wrote:
> > > On Mon, Mar 07, 2005 at 11:26:37AM -1000, Randy Bush wrote:
> > >
> > > > clues appreciated
> > >
> > > At xmpp.org, we had _jabber._tcp defined in DNS (old-style), but not
> > > _xmpp-server._tcp (new-style). Perhaps ejabberd does not gracefully
> > > degrade by handling _jabber._tcp SRV records?
> > >
> > > In any case, we've updated DNS for xmpp.org so connections should work
> > > again once our DNS changes propagate.
> > Hmm, it's still not working. Does ejabberd need to be restarted (e.g.,
> > does it cache SRV results)? The following command now yields the correct
> > results at the machine that hosts the psg.com server:
> > dig SRV _xmpp-server._tcp.xmpp.org
> Perhaps there's a DNS cache spoiling the fun. Just wait for the TTL to
> timeout. Or if it's about a new record, there's the retry period.
Does ejabberd cache DNS names? AFAIK, DNS has been updated at psg.com so
that the machine there now has the right information, but their jabber
server is not picking up the _xmpp-server._tcp SRV record.
More information about the ejabberd