From owner-freebsd-stable Sat Jan 27 23: 5:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.kconline.com (kconline.com [216.241.132.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A2B137B402 for ; Sat, 27 Jan 2001 23:05:16 -0800 (PST) Received: from barsoom (barsoom.kconline.com [216.241.133.19]) by mail.kconline.com (8.9.3/8.9.3) with SMTP id CAA18322; Sun, 28 Jan 2001 02:05:15 -0500 (EST) Message-ID: <03fc01c088f8$aafabd40$1385f1d8@kconline.com> From: "Mike Atkinson" To: , "Mike Tancsa" References: <4.2.2.20010127001841.03015358@marble.sentex.net> <4.2.2.20010127204048.013addb0@marble.sentex.net> Subject: Re: LAME domains, sendmail BIND and FreeBSD- its FreeBSD specific it seems (was more strange DNS issues in BIND and STABLE.)- Date: Sun, 28 Jan 2001 02:05:14 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Mike Tancsa" . > STABLE stock BIND+ sendmail 8.11.2: I can email LAME domains... This combination did not resolve the problem in our case but we built 8.11.2 from the ports tree. We did find that running Sendmail 8.9.3 (out of desperation) seems to have corrected the problem for now. We are still having intermittent problems with nslookups up on some domains (don't have the exact error message in debug mode, but it as an "NX" problem.) Sendmail 8.11.1 (or 8.11.2) does work fine if we set resolv.conf to use our competitors NT nameserver.. I am now getting ready to try what Dirk Meyer has suggested and will report back. ----- Mike Atkinson - mikea@kconline.com KC Online, Inc. - System Administration ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message