DNS usage in application protocols
Greg Hudson <ghudson@mit.edu> Thu, 24 August 2000 15:26 UTC
Received: from psg.com (psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19114 for <dnsext-archive@lists.ietf.org>; Thu, 24 Aug 2000 11:26:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.13 #1) id 13RyBP-000JBQ-00 for namedroppers-data@psg.com; Thu, 24 Aug 2000 07:40:43 -0700
Received: from rip.psg.com ([147.28.0.39]) by psg.com with esmtp (Exim 3.13 #1) id 13RyBP-000JBK-00 for namedroppers@ops.ietf.org; Thu, 24 Aug 2000 07:40:43 -0700
Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 13RyBP-000OT9-00 for namedroppers@ops.ietf.org; Thu, 24 Aug 2000 07:40:43 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Wed, 23 Aug 2000 21:19:13 -0400
Message-Id: <200008240119.VAA05833@egyptian-gods.MIT.EDU>
From: Greg Hudson <ghudson@mit.edu>
To: namedroppers@ops.ietf.org
Subject: DNS usage in application protocols
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
Hi. The following text appears in section 5 of draft-ietf-drums-smtpupd-12.txt, regarding MX hostnames with multiple A records: The destination host (perhaps taken from the preferred MX record) may be multihomed, in which case the domain name resolver will return a list of alternative IP addresses. It is the responsibility of the domain name resolver interface to have ordered this list by decreasing preference if necessary, and SMTP MUST try them in the order presented. My DNS background suggests that this "MUST try them in the order presented" requirement is misguided; order of DNS records is not supposed to be important. The text has been copied (with s/MX/SRV/) by a draft relevant to the IMPP group, so I'm concerned about a faulty meme propagating. Can people in this group comment on whether I'm off my rocker? I can't imagine a client wanting to tamper with the order of records returned by a resolver, but if for some odd reason it does want to (say, it happens to have some network map information, or a cached indication of which A record worked last time), I don't see why it should be a violation the standard. Thanks. to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body.
- DNS usage in application protocols Greg Hudson
- Re: DNS usage in application protocols Robert Elz
- Re: DNS usage in application protocols Terry Lambert