IETF Logo Mail Archive

Re: interop problems with getaddrinfo() address selection

der Mouse <mouse@Rodents.Montreal.QC.CA> Fri, 07 December 2007 18:28 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0hwS-0001Hr-WF; Fri, 07 Dec 2007 13:28:53 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1J0hwS-0001Hc-4Q for discuss-confirm+ok@megatron.ietf.org; Fri, 07 Dec 2007 13:28:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0hwR-0001HR-Qz for discuss@apps.ietf.org; Fri, 07 Dec 2007 13:28:51 -0500
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J0hwQ-0008U2-DG for discuss@apps.ietf.org; Fri, 07 Dec 2007 13:28:51 -0500
Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id NAA28966; Fri, 7 Dec 2007 13:28:47 -0500 (EST)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200712071828.NAA28966@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
Date: Fri, 07 Dec 2007 13:27:33 -0500
To: discuss@apps.ietf.org
Subject: Re: interop problems with getaddrinfo() address selection
In-Reply-To: <Pine.LNX.4.64.0712071735070.24448@hermes-1.csi.cam.ac.uk>
References: <Pine.LNX.4.64.0712061901020.24448@hermes-1.csi.cam.ac.uk> <200712062020.PAA16213@Sparkle.Rodents.Montreal.QC.CA> <Pine.LNX.4.64.0712071735070.24448@hermes-1.csi.cam.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

>> I'm interseted in what sort of problems it causes.
> DNS round robin is effective at balancing load evenly across multiple
> servers, because each client is (in effect) directed to one of the
> servers at random.  If the client sorts the DNS response before using
> it then the randomization is defeated and the load on the servers is
> no longer balanced.

Doh!  I knew I was missing something.  (What I was missing was looking
at the problem from the point of view of the servers, rather than the
clients.)

Thanks for the explanation.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

v2.14.0 | Report a Bug | By Email