From owner-freebsd-net@FreeBSD.ORG Fri Mar 28 01:13:31 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4544B1065672 for ; Fri, 28 Mar 2008 01:13:31 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from angel.comcen.com.au (angel.comcen.com.au [203.23.236.69]) by mx1.freebsd.org (Postfix) with ESMTP id D25E98FC1C for ; Fri, 28 Mar 2008 01:13:30 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.199] (202-172-126-254.cpe.qld-1.comcen.com.au [202.172.126.254]) by angel.comcen.com.au (8.13.4/8.12.9) with ESMTP id m2S10Yd2040240 for ; Fri, 28 Mar 2008 12:00:36 +1100 (EST) From: Da Rock To: freebsd-net@freebsd.org Content-Type: text/plain Date: Fri, 28 Mar 2008 11:00:23 +1000 Message-Id: <1206666023.4155.21.camel@laptop2.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) Content-Transfer-Encoding: 7bit X-comcen-MailScanner-Information: Please contact the ISP for more information X-comcen-MailScanner: Found to be clean X-comcen-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-16.43, required 4, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.37, BAYES_00 -15.00) X-comcen-MailScanner-From: rock_on_the_web@comcen.com.au Subject: DDNS, ISC-DHCPD, and Bind... not working because of strange error messages X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2008 01:13:31 -0000 (Sorry for cross posting- I originally sent this to the questions list but got no response, and on further reflection [considering the content] If figured that the most experience in these matters would exist here. If you don't mind, I'll stick around and watch this list so that I might learn something too :) ) I did actually manage to get this to work, and I can't exactly work out what changed to cause this error. I set this up at the end of last year, and it worked- kind of. The failure was my own by not using a proper FQDN, but it worked unofficially anyway. Records were updating etc: all happy. Anyway, I finally got the FQDN worked out (split horizon dns- external and internal views), but I find that the ddns is not working: and not because of the changes I made. I looked back and found the problem going on for month. My messages file has these entries, and no amount of googling has brought me any closer to finding out what they could mean, or why my clients aren't updating: Mar 27 16:18:54 {$HOSTNAME} dhcpd: pool.ntp.org: no A record associated with address I've edited the hostname to protect the innocent. What I can't figure out is why would dhcpd be looking at pool.ntp.org? I ran a dig on pool.ntp.org on the off chance it was busted- but of course it was not. And this record pops up everytime I renew my ip addresses. Weird... Little help anyone? Cheers