[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 28 Nov 2015 23:48:09 +0100
From: Jan Broer <jasiu.79@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Re: Would love to see reconsideration for domain and search
Hi Rich, i was wondering about the progress of implementing support for
'search' in resolv.conf. Is this on the road map?
Thanks!
On Tue, Oct 27, 2015 at 1:30 AM, Rich Felker <dalias@...c.org> wrote:
>
> I noticed in the process of trying to draft code to do this that there
> will be a lot of code duplication with the resolv.conf parsing in
> res_msend.c, and that this code has some stupid bugs (for example it
> stops parsing after it gets 3 nameservers, so it might miss options
> later in the file), so I think I'll take a look at factoring it into a
> new function to gather all the interesting information from
> resolv.conf that can be used in both places.
>
> A couple additional things I noticed from resolv.conf(5):
>
> 1. The default domain used by glibc is not the dns root but rather the
> domain portion of the local hostname determined by gethostname().
> Is there any value in duplicating this? Does anyone want/need it?
>
> 2. It's not clear from the documentation of "search" whether its
> presence overrides/suppresses the "domain" (default or set by
> resolv.conf) or adds additional searches before or after it. Which
> should it do?
>
> While glibc/legacy behavior is worth looking at, I don't think we need
> to look at things from a standpoint of exactly duplicating that.
> Meeting real-world modern application needs while avoiding
> inconveniencing users with stupid/unwanted behavior should be the
> primary goal.
>
> Rich
>
Content of type "text/html" skipped
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.
