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: Wed, 11 Jan 2023 12:18:33 -0500 [thread overview]
Message-ID: <20230111171832.GF4163@brightrain.aerifal.cx> (raw)
On Wed, Jan 11, 2023 at 12:33:59PM +0000, zhoujingqiang (A) wrote:
> Thanks for reply,
> It is not advisable to use localhost as a DNS server in embedded
> devices. It requires a resident process, which consumes many memory
> and bandwidth.
I hope you'll take the advice from others telling you why this isn't
the case, but regardless, the problem here is that you're asking for
something very different than what you actually want. You asked for a
higher MAXNS, but what you want is for the stub resolver to do
unioning for you. This is a much bigger request -- it's for policy
functionality that doesn't have existing precedent to be added to
libc. That's pretty much a hard no.
> We only provide devices, not servers. Servers are provided by
> carriers. We cannot write a build-in special servers on resolv.conf.
> Our devices need to be sold to carriers around the world. There are
> many small carriers. They have their own domain names, which are
> non-conflicting but unique. In this case, increasing the MAXNS limit
> is the simplest and most efficient way.I think raising MAXNS won't
> hurt anything.
If any of them returns NxDomain for a query that a different one
returns an answer for, they *are* conflicting. Only if they return the
same answer or ServFail/timeout would they be non-conflicting. It's
possible to setup non-conflicting private zones this way (with
ServFail) but not common practice and I doubt it's what they've done.
next prev parent reply other threads:[~2023-01-11 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 0:57 zhoujingqiang (A)
2023-01-10 16:28 ` 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).