From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 13:48:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B63716A4CE for ; Fri, 15 Oct 2004 13:48:55 +0000 (GMT) Received: from zen.rupture.net (zen.rupture.net [216.22.46.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCB1043D67 for ; Fri, 15 Oct 2004 13:48:54 +0000 (GMT) (envelope-from jon@rupture.net) Received: from zen.rupture.net (localhost [127.0.0.1]) by zen.rupture.net (8.13.1/8.13.1) with ESMTP id i9FDmq2E029302 for ; Fri, 15 Oct 2004 09:48:52 -0400 (EDT) (envelope-from jon@rupture.net) Received: (from jon@localhost) by zen.rupture.net (8.13.1/8.13.1/Submit) id i9FDmq0t029301 for freebsd-current@freebsd.org; Fri, 15 Oct 2004 09:48:52 -0400 (EDT) (envelope-from jon@rupture.net) X-Authentication-Warning: zen.rupture.net: jon set sender to jon@rupture.net using -f Received: by zen.rupture.net (tmda-sendmail, from uid 500); Fri, 15 Oct 2004 09:48:51 -0400 (EDT) Date: Fri, 15 Oct 2004 09:48:50 -0400 To: freebsd-current@freebsd.org Message-ID: <20041015134850.GB28548@zen.rupture.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i From: Jon Nathan Mail-Followup-To: freebsd-current@freebsd.org X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) X-Primary-Address: jon@rupture.net Subject: Re: BIND9 DNS problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jon Nathan List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 13:48:55 -0000 * Adam [10-11-2004 10:11]: > > Hey guys, > > When I try and query the machine from both it's external and internal IP, I > get no response for that zone what so ever, however when I attempt to query > the machine using localhost/loopback I get a proper answer. > Does anybody have a solution to this problem? It seems quite odd. Using your bind8 named.conf as a starting point prevented you from finding what appears to be a bind9 directive: // If named is being used only as a local resolver, this is a safe default. // For named to be accessible to the network, comment this option, specify // the proper IP address, or delete this option. // listen-on { 127.0.0.1; }; listen-on { 127.0.0.1; 1.2.3.4; }; -Jon -- Jon Nathan jon@rupture.net