From owner-freebsd-questions@FreeBSD.ORG Fri May 6 23:55:26 2005 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 A330916A4D4 for ; Fri, 6 May 2005 23:55:26 +0000 (GMT) Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57EA943DA2 for ; Fri, 6 May 2005 23:55:26 +0000 (GMT) (envelope-from freebsd@akruijff.dds.nl) Received: from smtp.planet.nl (ip51cc8423.speed.planet.nl [81.204.132.35]) by smtp14.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IG300E0SEGD87@smtp14.wxs.nl> for questions@freebsd.org; Sat, 07 May 2005 01:55:25 +0200 (CEST) Received: from Alex.lan (localhost [127.0.0.1]) by smtp.planet.nl (8.13.1/8.13.1) with ESMTP id j46NtGP7004797; Sat, 07 May 2005 01:55:16 +0200 Received: (from akruijff@localhost) by Alex.lan (8.13.1/8.13.1/Submit) id j46NtGYo004796; Sat, 07 May 2005 01:55:16 +0200 Content-return: prohibited Date: Sat, 07 May 2005 01:55:16 +0200 From: Alex de Kruijff In-reply-to: <20050506132055.26942164037@ws1-4.us4.outblaze.com> To: Fafa Hafiz Krantz Message-id: <20050506235516.GC3564@Alex.lan> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4.2.1i References: <20050506132055.26942164037@ws1-4.us4.outblaze.com> X-Authentication-warning: Alex.lan: akruijff set sender to freebsd@akruijff.dds.nl using -f cc: Jan Grant cc: questions@freebsd.org Subject: Re: What is --- WRONG --- with my network? 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: Fri, 06 May 2005 23:55:26 -0000 On Fri, May 06, 2005 at 08:20:54AM -0500, Fafa Hafiz Krantz wrote: > > > Unfortunately, you appear to be preemptively rejecting the most obvious > > advice, and implicitly asking that people start troubleshooting "from > > the middle". Was your machine up without reboot for months? If so, > > there's no guarantee that the state of named.conf actually reflects the > > state of the previously running named prior to a reboot (alas, I've seen > > this all too often). > > No, I had been rooting it quite often since I was testing PF. > > > Can you begin by posting your fully-functional named.conf and > > resolv.conf? And possibly describing exactly what you mean by "my > > nameserver is dysfunctional"? Do you mean that you cannot resolve > > addresses from your host? Does dig work against your local nameserver > > instance? Can you see any of the root servers with dig? Is named just > > refusing to start? ... and so on. > > # cat /var/named/etc/namedb/named.conf > # > > options { > directory "/etc/namedb"; > pid-file "/var/run/named/pid"; > }; I also have: dump-file "/var/dump/named_dump.db"; statistics-file "/var/stats/named.stats"; > > zone "." { > type hint; > file "named.root"; > }; > > zone "domain.com" { > type master; > file "db.domain.com"; > allow-transfer { 209.98.223.41; }; > }; > > zone "3.0.7.5.0.0.4.0.8.1.6.0.1.0.0.2.ip6.arpa" { > type master; > file "db.terrabionic.com.rev"; > allow-transfer { 209.98.223.41; }; > }; > > zone "terrabionic.lan" { > type master; > file "db.terrabionic.lan"; > }; > > zone "187.168.192.in-addr.arpa" { > type master; > file "db.terrabionic.lan.rev"; > }; > > zone "0.0.127.in-addr.arpa" { > type master; > file "db.localhost.rev"; > }; It could be that type slave files need to go in the subdirectory slave and type master files need to go in the subdirectory master. I have this: /* zone "example.com" { type slave; file "slave/example.com"; masters { 192.168.1.1; }; }; zone "0.168.192.in-addr.arpa" { type slave; file "slave/0.168.192.in-addr.arpa"; masters { 192.168.1.1; }; }; */ Check you /var/log/messages for errors about this. -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/