From: Srinivasa Raghavan <raghav135@gmail.com>
To: musl@lists.openwall.com, dalias@libc.org
Subject: Re: DNS resolution happenning only after timeout
Date: Wed, 4 Oct 2017 19:18:10 +0530 [thread overview]
Message-ID: <CAGpKtJ6FsKTY3VJBU_YpG9Xy1Nq1A5qjkpZfr8JcGs8BJw_iJw@mail.gmail.com> (raw)
In-Reply-To: <20170928165528.GA1627@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
Hi Rich,
Thanks for the reply.
Some updates:
1. Our DNS server is "Infoblox appliance".
2. When we had a delay, we found that there was a "AAAA" query along with
"A" query.
I did further debugging with "tcpdump" and able to narrow down on the
difference in behavior between "debian" and "alpine" images.
In debian:
If ipv6 is disabled (net.ipv6.conf.default.disable_ipv6 = 1)
Then the "nslookup" (or name resolution) does *not* do a "AAAA" query
In alpine:
If ipv6 is disabled (net.ipv6.conf.default.disable_ipv6 = 1)
Then the "nslookup" (or name resolution) does an "AAAA" query along with
"A" query
Is this intentional?
Also, I was wondering if there was any way to disable AAAA query in name
resolution?
Kind Regards,
Srinivasa Raghavan.
On Thu, Sep 28, 2017 at 10:25 PM, Rich Felker <dalias@libc.org> wrote:
> 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
>
[-- Attachment #2: Type: text/html, Size: 3889 bytes --]
next prev parent reply other threads:[~2017-10-04 13:48 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
2017-10-04 13:48 ` Srinivasa Raghavan [this message]
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=CAGpKtJ6FsKTY3VJBU_YpG9Xy1Nq1A5qjkpZfr8JcGs8BJw_iJw@mail.gmail.com \
--to=raghav135@gmail.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.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).