Date: Thu, 24 Jul 2003 15:02:15 -0700 From: "Derrick Ryalls" <ryallsd@datasphereweb.com> To: <questions@freebsd.org> Subject: Bind9 Issue Message-ID: <003801c3522f$415de940$0200a8c0@bartxp>
next in thread | raw e-mail | index | archive | help
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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003801c3522f$415de940$0200a8c0>