From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28111 invoked from network); 10 Jan 2023 16:29:02 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 10 Jan 2023 16:29:02 -0000 Received: (qmail 9247 invoked by uid 550); 10 Jan 2023 16:28:58 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 8191 invoked from network); 10 Jan 2023 16:28:57 -0000 Date: Tue, 10 Jan 2023 11:28:45 -0500 From: Rich Felker To: "zhoujingqiang (A)" Cc: "musl@lists.openwall.com" , liudongxu , "Yulu(Brooklyn,RTOS)" , Nixiaoming , Wangxu , qiuguorui , "wangyunhe (A)" Message-ID: <20230110162844.GE4163@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] MAXNS should be increased On Tue, Jan 10, 2023 at 12:57:34AM +0000, zhoujingqiang (A) wrote: > Hello, > > 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[1]. The concern is that changing MAXNS > would cause an ABI break. Musl does not have this problem since > __res_state is stub. > [1]: 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. Rich