From owner-freebsd-questions@FreeBSD.ORG Fri Oct 6 12:36:33 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 6F5B516A412 for ; Fri, 6 Oct 2006 12:36:33 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D6843D5C for ; Fri, 6 Oct 2006 12:36:28 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from localhost (monrovll-cuda1-24-53-251-44.pittpa.adelphia.net [24.53.251.44]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Fri, 06 Oct 2006 08:36:28 -0400 id 0005641F.45264DCC.00016493 Date: Fri, 6 Oct 2006 08:36:26 -0400 From: Bill Moran To: Wojciech Puchar Message-Id: <20061006083626.a2fd67a6.wmoran@collaborativefusion.com> In-Reply-To: <20061006142718.T74782@chylonia.3miasto.net> References: <20061006105745.V54913@chylonia.3miasto.net> <20061006072907.cf58999a.wmoran@collaborativefusion.com> <20061006142718.T74782@chylonia.3miasto.net> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: strange DNS problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2006 12:36:33 -0000 Wojciech Puchar wrote: > >> > >> where's a problem? while hostr is able to get IP addresses but then > >> reports servfail? > > > > I don't see that error when I try the same lookups. > > host -t a hermes01.mil.be > > hermes01.mil.be has address 194.7.21.40 > > hermes01.mil.be has address 193.191.219.40 > > > > I suspect the problem is in your resolver config and/or caches. > > > possibly. but where to look? no other site behaves like this. > > my named.conf: > > acl seconds { 153.19.176.2; 10.254.1.254; 83.16.196.26;}; > acl locals {10/8; 127.0.0.1/32;}; > > options { > directory "/etc/namedb"; > allow-transfer {seconds;}; > pid-file "/var/run/named/pid"; > dump-file "/var/dump/named_dump.db"; > statistics-file "/var/stats/named.stats"; > listen-on { 127.0.0.1; 10.254.1.248; 83.18.148.142; }; > listen-on-v6 { any; }; > }; > #logging {category lame-servers { null; };}; > > zone "." in {type hint; file "root.cache";}; > zone "0.0.127.in-addr.arpa" in { type master; file "127";}; > > and then master and slaves domains definitions below. Just a theory: Do you possibly have recursive queries locked down too far, and does resolution of that name require recursion? -- Bill Moran I lay down for a while, and I woke up on the ocean, floating on my back, and staring at the grey. It was completely still, 'cept for the pounding of my heart, was bring me back to life, from three strange days.