[jadmin] _jabber._tcp SRV record at jabber.org
stpeter at jabber.org
Tue Jan 30 17:56:20 CST 2007
FYI, I have removed support at the jabber.org domain for the old and
deprecated _jabber._tcp SRV record. If your server now has trouble
connecting to the jabber.org server, update your DNS to instead support
the _xmpp-server._tcp SRV record.
-------- Original Message --------
Subject: Re: [Standards] UPDATED: XEP-0156 (A DNS TXT Resource Record
Format for XMPP Connection Methods)
Date: Tue, 30 Jan 2007 16:46:19 -0700
From: Peter Saint-Andre <stpeter at jabber.org>
Reply-To: XMPP Extension Discussion List <standards at xmpp.org>
To: XMPP Extension Discussion List <standards at xmpp.org>
References: <20070130180948.0D2AC21A4F8 at atlas.jabber.org>
<45BFCE65.5030300 at tthias.eu> <45BFD23D.1030505 at jabber.org>
<45BFD50C.9040503 at tthias.eu>
Matthias Wimmer wrote:
> Hi Peter!
> Peter Saint-Andre schrieb:
>>> For compatibility we already have to do up to four DNS lookups:
>>> _xmpp-server SRV
>>> _jabber SRV
>> Let's deprecate _jabber SRV, shall we? I have already removed any text
>> about it from rfc3920bis (version -01).
> I already consider it to be deprecated. What I think would be needed it,
> that we should make an agreement between the server implementors, that
> we will remove support for this record in future releases of our server
> Especially if prominent servers as "jabber.org" would stop
> resolving this record, administrators needing a SRV record would soon
> notice, that they have to update their DNS.
> And we could create some scripts before, that check the DNS entries of
> the peers of some servers, if they contain a _jabber._tcp SRV record,
> but no _xmpp-server._tcp SRV record. This could be used to notify the
> admins of such servers as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jadmin/attachments/20070130/3da4df36/smime.bin
More information about the JAdmin