Date: Thu, 28 Sep 2017 12:55:28 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Cc: Srinivasa Raghavan <raghav135@...il.com> Subject: Re: DNS resolution happenning only after timeout On Thu, Sep 28, 2017 at 12:28:55PM +0200, Szabolcs Nagy wrote: > * Srinivasa Raghavan <raghav135@...il.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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.