From owner-freebsd-isp Thu Feb 22 9:13:28 2001 Delivered-To: freebsd-isp@freebsd.org Received: from humid.lightning.net (humid.lightning.net [209.51.160.9]) by hub.freebsd.org (Postfix) with SMTP id E7FE737B491 for ; Thu, 22 Feb 2001 09:13:23 -0800 (PST) (envelope-from jreddy@lightning.net) Received: (qmail 89948 invoked from network); 22 Feb 2001 17:10:12 -0000 Received: from nut.lightning.net (209.51.160.16) by humid.lightning.net with SMTP; 22 Feb 2001 17:10:12 -0000 Message-Id: <5.0.2.1.2.20010222115101.00aa29a0@mailhost.lightning.net> X-Sender: jreddy@lightning.net@mailhost.lightning.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 22 Feb 2001 12:05:18 -0500 To: From: John Reddy Subject: RE: annoying denied dns updates from lame nt/2000 servers In-Reply-To: References: <3A909F0D.549C38D1@confusion.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What about a scenario of a user base of tens of thousands, via DSL, cable modem, dialup, etc. Getting hundreds or thousands of customers with Win2k running, and running dynamic update. That's the situation that needs to be addressed. Going to all my customers to tell them what to do isn't quite the answer I'm hoping for. What can I do from my end, in terms of commands in BIND to prevent logging of these updates? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message