From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: Re: Would love to see reconsideration for domain and search
Date: Fri, 23 Oct 2015 11:35:27 +0200 [thread overview]
Message-ID: <5629FF5F.8060004@skarnet.org> (raw)
In-Reply-To: <20151023081259.GX28311@example.net>
On 23/10/2015 10:12, u-uy74@aetey.se wrote:
> +1 to the level 1 comments
>
> +1 to solving the particular problem of a certain deployment
> (the massive reliance on search paths)
> inside the deployment, not in a general purpose library
>
> It looks unrealistic to both have redundancy and differing/conflicting
> data on different servers in a consistent fashion, by the mere mechanisms
> of resolv.conf.
>
> Nice that musl chose consistency and redundancy.
>
> Good if there is an option suitable for systems which need differing
> functionality, but please not at an extra cost for other parties.
>
> A DNS cache looks of course like the right option for fine tuning the
> desired resolution behaviour.
+1 to all this.
"search" in /etc/resolv.conf was *never* meant to list resolvers
serving different results. It was always meant to list backups
serving consistent results. Any other use of "search" lines is
abusing the mechanism; if it works with glibc, it is a testimony
that glibc doesn't care about consistency, not an argument that it
is a valid use case. The right way to proceed is to implement an
ad-hoc resolver that suits the specific wanted usage, not to
modify a libc that implements the proper behaviour.
--
Laurent
next prev parent reply other threads:[~2015-10-23 9:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 21:24 Tim Hockin
2015-10-22 21:56 ` Rich Felker
2015-10-22 22:36 ` Tim Hockin
2015-10-22 23:00 ` Josiah Worcester
2015-10-22 23:37 ` Tim Hockin
2015-10-23 4:27 ` Rich Felker
2015-10-23 5:13 ` Tim Hockin
2015-10-23 5:31 ` Rich Felker
2015-10-23 5:37 ` Tim Hockin
2015-10-23 6:00 ` Rich Felker
2015-10-23 6:04 ` Tim Hockin
2016-01-29 0:57 ` Rich Felker
2015-10-27 0:30 ` Rich Felker
2015-10-27 0:37 ` Tim Hockin
2015-10-27 0:45 ` Rich Felker
2015-10-27 8:11 ` u-uy74
2015-11-28 22:48 ` Jan Broer
2015-11-28 23:20 ` Rich Felker
2015-11-29 3:06 ` Jan Broer
2016-01-29 0:58 ` Rich Felker
2015-10-26 2:14 ` Re: Would not " John Levine
2015-10-26 5:14 ` Tim Hockin
2015-10-26 16:16 ` Rich Felker
2015-10-26 17:41 ` John Levine
2015-10-26 18:08 ` Rich Felker
2015-10-23 8:12 ` Re: Would " u-uy74
2015-10-23 9:35 ` Laurent Bercot [this message]
2015-10-23 12:23 ` Laurent Bercot
2015-10-23 15:57 ` Tim Hockin
2015-10-23 5:26 ` Kurt H Maier
2015-10-24 21:33 ` Tim Hockin
2015-10-24 21:57 ` Kurt H Maier
2015-10-24 23:31 ` Rich Felker
2015-10-24 22:02 ` Rich Felker
2015-10-24 22:32 ` Tim Hockin
2015-10-25 8:20 ` u-uy74
2015-10-25 13:06 ` Jan Broer
2015-10-25 13:19 ` u-uy74
2015-10-25 13:39 ` Jan Broer
2015-10-25 14:08 ` u-uy74
2015-10-25 19:08 ` Rich Felker
2015-10-26 1:26 ` Isaac Dunham
2015-10-26 15:35 ` Rich Felker
2015-10-23 15:30 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=5629FF5F.8060004@skarnet.org \
--to=ska-dietlibc@skarnet.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).