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=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16407 invoked from network); 8 Sep 2021 15:31:16 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 8 Sep 2021 15:31:16 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Wed Sep 8 11:19:42 -0400 2021 Message-ID: Date: Wed, 08 Sep 2021 17:19:31 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: compliant non-blocking descriptor-based rails Subject: [9front] latest dns change Reply-To: 9front@9front.org Precedence: bulk Hash: 41369692bf818fdee290d357bdb27fdb71487b92 Author: cinap_lenrek Date: Wed Sep 8 15:34:23 +0200 2021 ndb/dns: fix wrong ndb attribute "txtrr" vs. "txt" for caching server i just fixed a bug where the caching logic of dns code would look for txtrr= ndb attribute instead of the documented txt= attribute. this is an inconsistency bug, as the ndb lookup code *without caching* would look for txt= while the *caching* code looked for txtrr=. it is now change to txt=. txtrr= is no longer supported! in case you have this in your ndb configuration, please fix it and change to txt= -- cinap