From owner-freebsd-questions Tue Dec 12 19:24:46 2000 From owner-freebsd-questions@FreeBSD.ORG Tue Dec 12 19:24:44 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mailbox.mcs.net (Mailbox.mcs.com [192.160.127.87]) by hub.freebsd.org (Postfix) with ESMTP id 6442637B400 for ; Tue, 12 Dec 2000 19:24:44 -0800 (PST) Received: (from tforrest@localhost) by mailbox.mcs.net (8.9.3/8.9.3) id VAA00809; Tue, 12 Dec 2000 21:24:43 -0600 (CST) (envelope-from tforrest) Message-Id: <200012130324.VAA00809@mailbox.mcs.net> From: "Tommy Forrest - KE4PYM" To: "freebsd-questions@FreeBSD.ORG" Date: Tue, 12 Dec 2000 22:26:51 -0500 Reply-To: "Tommy Forrest - KE4PYM" Priority: Normal X-Mailer: BluePrint Software Works PMMail2000 with Bandit Tagger98 In-Reply-To: <20001213031900.14711.qmail@web3302.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Tag: Bandit Tagger98 - Registered to : KE4PYM Subject: Dynamic DNS updates with DHCPd/client Sender: tforrest@mailbox.mcs.net Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy folks. I make use of dyndns.org. Today I received a note saying that one of my systems was attempting to update their zone files. Taking a look at my DHCP man pages I see that dynamic DNS updating is supported with isc-dhcp3-3.0.b1.17 (I'm working on upgrading). The man pages mention the ability to turn off the file in the README doc - WHICH I READ, but did not find any reference to shutting this feature off. I've told dhcpd to only run on my xl1 (internal interface) and not xl0 (my public interface), and I find it odd that dhcpd would be trying to do this. Any ideas? Tommy Forrest - KE4PYM - tforrest@mcs.net http://www.mcs.net/~tforrest And now, its time, for some useless, bandwidth wasting words of wisdom: OS/2: Windows with bullet-proof glass. PGP Public Key Fingerprint: E1FD 1327 D9D6 3D9A 6D5E 21CF 902D 41FC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message