mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: Re: Would love to see reconsideration for domain and search
Date: Fri, 23 Oct 2015 14:29:19 -0400	[thread overview]
Message-ID: <20151023182919.GK8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <CA+MmhbNCZ7S8_9euE2rJjMe0S76DM7Lgo5CQvwvt7qOa4V_r+g@mail.gmail.com>

On Fri, Oct 23, 2015 at 07:40:45PM +0200, Jan Broer wrote:
> >I think that is where we have arrived (except it's < and >= in your
> >expressions).  Kubernetes will have to change some to satisfy the
> >assumed fungibility of nameservers, but it's the direction things are
> >almost certainly moving anyway.
> 
> Hi Tim, i guess i skipped these last message - sorry.
> 
> If you could clear this up for me:
> When there are multiple nameservers, does the musl resolver return the
> first response it receives regardless of it's status?
> So even when it is something like SERVFAIL or REFUSED it will not wait for
> the responses from the other nameservers that might be positive?

No. musl basically ignores and response except success or nxdomain.
Actually servfail is treated specially and results in a limited number
of immediate retries because there are a lot of broken nameservers
that return servfail but immediately succeed on a second try, and
doing the immediate retry drastically speeds up queries in such
environments.

In any case, only success or nxdomain are treated as results
reportable to the caller. Otherwise musl waits for one of these and
returns a transient failure (not does-not-exist) if it times out.

Rich


  parent reply	other threads:[~2015-10-23 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 15:30 Jan Broer
2015-10-23 16:01 ` Tim Hockin
2015-10-23 17:40   ` Jan Broer
2015-10-23 18:02     ` Tim Hockin
2015-10-23 18:03     ` Jan Broer
2015-10-23 18:29     ` Rich Felker [this message]
2015-10-23 21:27       ` Jan Broer

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=20151023182919.GK8645@brightrain.aerifal.cx \
    --to=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).