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 8051 invoked from network); 10 Feb 2021 15:30:10 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 10 Feb 2021 15:30:10 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 1ess; Wed Feb 10 10:24:11 -0500 2021 Received: from [127.0.0.1] ([104.59.85.219]) by 5ess; Wed Feb 10 10:24:10 -0500 2021 Date: Wed, 10 Feb 2021 10:24:09 -0500 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <1B74CAEE535895AEA8BD0EFB600EF335@hog> References: <1B74CAEE535895AEA8BD0EFB600EF335@hog> Message-ID: <2E14A3D4-55FC-419A-9289-7D3229E692AE@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: stable advanced CMS NoSQL frontend Subject: Re: [9front] transient dns errors cause smtp failure Reply-To: 9front@9front.org Precedence: bulk On February 7, 2021 8:56:39 AM EST, kvik@a-b=2Exyz wrote: >I think I found a reason for DNS failing on known good domains=2E > >/sys/src/cmd/ndb/dns=2Eh:156,157 > /* tune; was 60*1000; keep it short */ > Maxreqtm=3D 8*1000, /* max=2E ms to process a request */ anyone remember when/why this was ever changed? our hg log comments on cha= nges that touched this file have sometimes been vague=2E sl