From owner-freebsd-questions@FreeBSD.ORG Thu Jul 24 15:02:26 2003 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 7A7F337B401 for ; Thu, 24 Jul 2003 15:02:26 -0700 (PDT) Received: from datasphereweb.com (12-212-67-226.client.attbi.com [12.212.67.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D3FCB43F3F for ; Thu, 24 Jul 2003 15:02:25 -0700 (PDT) (envelope-from ryallsd@datasphereweb.com) Received: (qmail 46778 invoked from network); 24 Jul 2003 22:02:25 -0000 Received: from evrtwa1-ar17-4-47-114-001.evrtwa1.dsl-verizon.net (HELO bartxp) (4.47.114.1) by datasphereweb.com with SMTP; 24 Jul 2003 22:02:25 -0000 From: "Derrick Ryalls" To: Date: Thu, 24 Jul 2003 15:02:15 -0700 Message-ID: <003801c3522f$415de940$0200a8c0@bartxp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: Bind9 Issue 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: Thu, 24 Jul 2003 22:02:26 -0000 I bought a domain for my gaming clan and installed bind9 specifically for the views feature. The DNS machine is my home router and our gaming machine is on another network and physically 60 miles away and is nat'ed on a lan. The lan the game server is on has it's own DNS machine, but is located behind the same public ip. I have DNS setup up so that any requests for www.gameserver.org (name different to protect the ignorant) that come from that lan get the ip 192.168.1.20, the machines internal ip. When logged into the game server, I can do a dig www.gameserver.org and the correct ip comes back. The problem is that When I dig www.gameserver.org @, it responds with the public ip, not the internal and therefore won't work for the lan. Talking with workers at that site, their DNS forwards to just the root servers, not their local ISP DNS. Any ideas on how I can track this down and get the internal ip listed for just the users of the lan? -Derrick