From owner-freebsd-questions Tue Jan 28 7:49:10 2003 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 7188537B401 for ; Tue, 28 Jan 2003 07:49:08 -0800 (PST) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF15B43F43 for ; Tue, 28 Jan 2003 07:49:06 -0800 (PST) (envelope-from leblanc@keyslapper.org) Received: from keyslapper.org ([68.160.24.118]) by out001.verizon.net (InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with ESMTP id <20030128154906.RUVT23484.out001.verizon.net@keyslapper.org> for ; Tue, 28 Jan 2003 09:49:06 -0600 Received: from keyslapper.org (localhost [127.0.0.1]) by keyslapper.org (8.12.3/8.12.3) with ESMTP id h0SFn7O2042925 for ; Tue, 28 Jan 2003 10:49:07 -0500 (EST) (envelope-from leblanc@keyslapper.org) Received: (from leblanc@localhost) by keyslapper.org (8.12.3/8.12.3/Submit) id h0SFn6gF042924 for freebsd-questions@FreeBSD.org; Tue, 28 Jan 2003 10:49:06 -0500 (EST) Date: Tue, 28 Jan 2003 10:49:06 -0500 From: Louis LeBlanc To: FreeBSD Questions Subject: more named questions . . . Message-ID: <20030128154906.GA41066@keyslapper.org> Reply-To: freebsd-questions@FreeBSD.org Mail-Followup-To: FreeBSD Questions Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.3i X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.160.24.118] at Tue, 28 Jan 2003 09:49:05 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been working on setting up named in a sandbox. I got some helpful hints here where I couldn't quite understand the handbook (yes, I did read it, that doesn't necessarily mean I understood it :). Anyway, I followed the handbook steps for sandboxing named exactly - meaning I didn't even retype the commands, but copied them by mouse from the handbook page. This part is giving me some trouble: # Symlink /var/run/ndc to /etc/namedb/var/run/ndc: # ln -sf /etc/namedb/var/run/ndc /var/run/ndc Note: This simply avoids having to specify the -c option to ndc(8) every time you run it. Since the contents of /var/run are deleted on boot, if this is something that you find useful you may wish to add this command to root's crontab, making use of the @reboot option. See crontab(5) for more information regarding this. What are the chances this is wrong? After completing the section, I typed 'ndc start' at the root prompt, and got the following: # ndc start ndc: error: name server has not started (yet?) So I tried to stop it: # ndc stop ndc: error: ctl_client: evConnect(fd 3): No such file or directory ndc: error: cannot connect to command channel (/var/run/ndc) And this didn't even stop named. Something had to be wrong. I did a little more reading, and it looked to me like that command should have been the other way around. So I tried the following: # rm /var/run/ndc # ln -s /var/run/ndc /etc/namedb/var/run/ndc # ndc start new pid is 42557 then, just to be sure: # ndc stop and named did quit. Did I stumble on a typo in the handbook? And if so, did I also stumble on the CORRECT way to do it? And, finally, once I got named started in this manner, I got the following message in the /var/log/messages: Jan 28 10:41:04 keyslapper named[42779]: check_hints: A records for J.ROOT-SERVERS.NET class 1 do not match hint records Doing a lookup, host gave 192.58.128.30 as the correct IP, but named.root had 198.41.0.10. When I changed named.root and restarted named, the message went away. Anyone else ever have this kind of problem? TIA Lou -- Louis LeBlanc leblanc@keyslapper.org Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ QOTD: "I'm not really for apathy, but I'm not against it either..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message