mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Srinivasa Raghavan <raghav135@gmail.com>
Subject: Re: DNS resolution happenning only after timeout
Date: Thu, 28 Sep 2017 12:55:28 -0400	[thread overview]
Message-ID: <20170928165528.GA1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170928102854.GI15263@port70.net>

On Thu, Sep 28, 2017 at 12:28:55PM +0200, Szabolcs Nagy wrote:
> * Srinivasa Raghavan <raghav135@gmail.com> [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 <name>
> > 2. nslookup <name>
> > 3. traceroute <name>
> > 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


  reply	other threads:[~2017-09-28 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 10:15 Srinivasa Raghavan
2017-09-28 10:28 ` Szabolcs Nagy
2017-09-28 16:55   ` Rich Felker [this message]
2017-10-04 13:48     ` Srinivasa Raghavan
2017-10-04 16:46       ` Markus Wichmann
2017-10-04 19:28         ` Srinivasa Raghavan
2017-10-04 20:18           ` Rich Felker
2017-10-04 20:39             ` Srinivasa Raghavan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170928165528.GA1627@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=raghav135@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).