From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12658 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: [PATCH] resolver: only exit the search path loop there are a positive number of results given Date: Fri, 30 Mar 2018 22:24:31 +0200 Message-ID: <20180330202431.GE4418@port70.net> References: <20180330185225.29656-1-nenolod@dereferenced.org> <20180330191452.GS1436@brightrain.aerifal.cx> <20180330193548.GT1436@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1522441368 11051 195.159.176.226 (30 Mar 2018 20:22:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 30 Mar 2018 20:22:48 +0000 (UTC) User-Agent: Mutt/1.9.1 (2017-09-22) To: musl@lists.openwall.com Original-X-From: musl-return-12672-gllmg-musl=m.gmane.org@lists.openwall.com Fri Mar 30 22:22:44 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1f20Xr-0002n6-Up for gllmg-musl@m.gmane.org; Fri, 30 Mar 2018 22:22:44 +0200 Original-Received: (qmail 31778 invoked by uid 550); 30 Mar 2018 20:24:44 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 31756 invoked from network); 30 Mar 2018 20:24:43 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:12658 Archived-At: * William Pitcock [2018-03-30 14:44:44 -0500]: > There is a talk in a few weeks at Kubecon (the Kubernetes conference), > explicitly titled "Don't Use Alpine If You Care About DNS." The talk > largely centers around how musl's overly strict behaviour makes Alpine > a bad choice for "the real world." I would like to turn this into a > story where we can announce that Alpine 3.8 mitigates this problem > instead, doing such will be good for both Alpine and the musl > ecosystem as a whole, as it is defanging a point of possible FUD. musl has had a good track record catching bugs in dns implementations and in dns setups, i don't think this should be mitigated, it's good to know that cloudflare has a broken dns server, or that kubernetes had dns setup bugs, these are real reliability and performance issues affecting all systems not just musl.