From owner-freebsd-questions@FreeBSD.ORG Wed Feb 18 03:51:14 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA6CE16A4CE for ; Wed, 18 Feb 2004 03:51:14 -0800 (PST) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50BB43D2D for ; Wed, 18 Feb 2004 03:51:13 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i1IBpAr17592; Wed, 18 Feb 2004 22:51:10 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id DF02D32E; Wed, 18 Feb 2004 22:51:08 +1100 (EST) Date: Wed, 18 Feb 2004 22:51:08 +1100 From: Tony Frank To: Ajitesh K Message-ID: <20040218115108.GD289@marvin.home.local> References: <06ba01c3f58c$8c484940$3a02010a@wcox> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <06ba01c3f58c$8c484940$3a02010a@wcox> User-Agent: Mutt/1.4.2i cc: FreeBSD Questions Subject: Re: Name Server error / problem with Win XP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 11:51:14 -0000 Hi there, On Tue, Feb 17, 2004 at 02:30:49PM -0500, Ajitesh K wrote: > We are running "NameServ1" Name server on Freebsd 4.8 > We are getting some kind of error on my name server "nameserv1". FYI, "TM25" > is laptop of out side client and OS is Windows XP Home. > nameserv1.lan.company.com kernel log messages: > > > 31 10:47:32 nameserv1 dhcpd: if IN A TM25.dhcp.company.com domain doesn't > exist add 300 IN A TM25.dhcp.company.com 10.1.2.165 add 300 IN TXT > TM25.dhcp.company.com "31eb2f5e58786ebab0b6eabd298b28671f": domain already > exists > > I feel its some thing to do with Windows XP. Does any one know the fix? You have your dhcpd configured to use 'dynamic dns' function. When the laptop gets an address via dhcp, the dhcpd sends a message to dns to update the dns name to the new IP address. Some windows clients can do this also if the option is configured in the Windows DNS settings. Here I think it is your server as the log line comes from "dhcpd". In this case, the name "TM25.dhcp.company.com" already exists so dhcpd reports this. This may be due to a static entry in DNS zone files or because the laptop already had an entry configured earlier. You can check by doing a 'dig TM25.dhcp.company.com' and see what results you get from your DNS - you should see the name resolve to the IP address of the laptop. Regards, Tony