From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 2 20:48:03 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C75016A4CE for ; Wed, 2 Feb 2005 20:48:03 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A4F43D2F for ; Wed, 2 Feb 2005 20:48:02 +0000 (GMT) (envelope-from garycor@comcast.net) Received: from [10.56.78.111] (pcp09118143pcs.union01.nj.comcast.net[69.142.234.88]) by comcast.net (sccrmhc13) with ESMTP id <20050202204801016005i864e>; Wed, 2 Feb 2005 20:48:01 +0000 Message-ID: <42013CCD.9090007@comcast.net> Date: Wed, 02 Feb 2005 15:49:17 -0500 From: Gary Corcoran User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt References: <420092FA.1090906@comcast.net> In-Reply-To: <420092FA.1090906@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: cahe-only DNS in jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 20:48:03 -0000 Matt wrote: > I'm experiencing strange behaviour with Bind running inside a jail. I'm > running 5.2.1 current in the jail. Thinks are working, but poorly. > Lookups for my local machines work perfectly. Some remote lookups work > fine (yahoo, google, etc...). However, many lookups time out, but will > succeed after a few tries. I'm doing all this from home (comcast cable > internet). Anyway, I'm not sure what to do. Sniffing the network > doesn't seem to help much. Queries and requests are reaching the right > hosts and ports. Thanks for any help. I don't know if this applies to you, but about yesterday my PC's stopped working w/r/t DNS lookups. Comcast changed the IP addresses of their DNS servers. For a while they had one new one, but one of the old ones worked. But yesterday the old IP address stopped working completely, forcing me to update my configuration files... Gary > dnshost# uname -a > FreeBSD dnshost 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 > 20:45:55 GMT 2004 > root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 > > dnshost# named -v > named 8.3.7-REL Sun Jan 2 13:17:40 PST 2005 > root@tmodel.my.domain:/usr/obj/usr/src/usr.sbin/named > > dnshost# nslookup www.washington.edu > Server: localhost > Address: 127.0.0.1 > > *** localhost can't find www.washington.edu: Server failed > dnshost# !! > nslookup www.washington.edu > Server: localhost > Address: 127.0.0.1 > > Non-authoritative answer: > Name: www.washington.edu > Addresses: 140.142.15.233, 140.142.3.7, 140.142.3.35, 140.142.15.163 > > dnshost# !! > nslookup www.usenix.org > Server: localhost > Address: 127.0.0.1 > > Non-authoritative answer: > Name: db.usenix.org > Address: 131.106.3.253 > Aliases: www.usenix.org > > options { > directory "/etc/namedb"; > pid-file "/var/run/named/pid"; > }; > > zone "." { > type hint; > file "tables/named.root"; > }; > > zone "0.0.127.IN-ADDR.ARPA" { > type master; > file "tables/db.localhost"; > }; > > zone "hersant.dyndns.org" { > type master; > file "tables/db.hersant.dyndns.org"; > }; > > zone "2.168.192.in-addr.arpa" { > type master; > file "tables/db.2.168.192.in-addr.arpa"; > };