From: Rich Felker <email@example.com>
To: "zhoujingqiang (A)" <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>,
Nixiaoming <email@example.com>, Wangxu <firstname.lastname@example.org>,
"wangyunhe (A)" <email@example.com>
Subject: Re: [musl] MAXNS should be increased
Date: Tue, 10 Jan 2023 11:28:45 -0500 [thread overview]
Message-ID: <20230110162844.GE4163@brightrain.aerifal.cx> (raw)
On Tue, Jan 10, 2023 at 12:57:34AM +0000, zhoujingqiang (A) wrote:
> Currently, MAXNS is set to 3 which limits the number of nameserver.
> It is not enough to meet most people's requirements for private DNS
> servers. In my scenario, my client needs to access the networks of
> six companies. Each company provides active/standby servers to
> obtain private domain names. Three DNS servers are far from enough.
> Expect to increase MAXNS to 12
> Glibc has similar open bug. The concern is that changing MAXNS
> would cause an ABI break. Musl does not have this problem since
> __res_state is stub.
> : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998211
> I am not subscribed and want to be Cc'd on replies, thanks.
Multiple nameservers in resolv.conf are not a means to do unioning of
conflicting DNS namespaces. They're expected to be purely redundant
with non-conflicting (i.e. if one doesn't know about something another
does, it has to ignore the query or ServFail, not NxDomain or NODATA
it) records. If you need unioning of distinct spaces using custom
rules for resolving conflicts, you need a special nameserver running
on localhost or somewhere else you control that performs this logic.
next prev parent reply other threads:[~2023-01-10 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 0:57 zhoujingqiang (A)
2023-01-10 16:28 ` Rich Felker [this message]
2023-01-11 12:33 zhoujingqiang (A)
2023-01-11 15:38 ` Joakim Sindholt
2023-01-11 15:53 ` Laurent Bercot
2023-01-11 17:18 ` Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).