From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11957 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: DNS resolution happenning only after timeout Date: Thu, 28 Sep 2017 12:55:28 -0400 Message-ID: <20170928165528.GA1627@brightrain.aerifal.cx> References: <20170928102854.GI15263@port70.net> 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 1506617746 15344 195.159.176.226 (28 Sep 2017 16:55:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 28 Sep 2017 16:55:46 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Srinivasa Raghavan To: musl@lists.openwall.com Original-X-From: musl-return-11970-gllmg-musl=m.gmane.org@lists.openwall.com Thu Sep 28 18:55:41 2017 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 1dxc65-0003La-AK for gllmg-musl@m.gmane.org; Thu, 28 Sep 2017 18:55:37 +0200 Original-Received: (qmail 26035 invoked by uid 550); 28 Sep 2017 16:55:41 -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 26012 invoked from network); 28 Sep 2017 16:55:41 -0000 Content-Disposition: inline In-Reply-To: <20170928102854.GI15263@port70.net> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:11957 Archived-At: On Thu, Sep 28, 2017 at 12:28:55PM +0200, Szabolcs Nagy wrote: > * Srinivasa Raghavan [2017-09-28 15:45:28 +0530]: > > When using "Alpine" docker image which uses musl-libc, we are facing delay > > when we do operations like below in our production environment, > > 1. ping > > 2. nslookup > > 3. traceroute > > 4. http request from node.js > > > > this bug may be related: > https://github.com/rancher/rancher/issues/9961 Yes, I just filed it after reading the discussion on IRC and this bug report that was linked as describing similar behavior: https://github.com/rancher/rancher/issues/4177#issuecomment-332571951 This really requires a fix on the rancher-dns side. I'm not sure exactly what glibc is doing, but it couldn't be giving the behavior you want without doing something wrong: it's falling back and trying different search domains when it hasn't been told that the first one doesn't exist, only that the nameserver is experiencing a problem. Rich