Date: Fri, 25 Jul 2003 10:30:22 +1200 From: Jonathan Chen <jonc@chen.org.nz> To: Derrick Ryalls <ryallsd@datasphereweb.com> Cc: questions@freebsd.org Subject: Re: Bind9 Issue Message-ID: <20030724223022.GA78422@grimoire.chen.org.nz> In-Reply-To: <003801c3522f$415de940$0200a8c0@bartxp> References: <003801c3522f$415de940$0200a8c0@bartxp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 24, 2003 at 03:02:15PM -0700, Derrick Ryalls wrote:
> 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 <my DNS ip> and the correct ip
> comes back. The problem is that When I dig www.gameserver.org @<the
> lan's DNS machine>, it responds with the public ip, not the internal and
> therefore won't work for the lan.
You're going to have to show us the named.conf, before anyone will
answer.
--
Jonathan Chen <jonc@chen.org.nz>
----------------------------------------------------------------------
"Beer. Now there's a temporary solution."
- Homer Simpson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030724223022.GA78422>