Date: Thu, 24 Jul 2003 16:18:55 -0700 From: "Derrick Ryalls" <ryallsd@datasphereweb.com> To: "'Jonathan Chen'" <jonc@chen.org.nz> Cc: questions@freebsd.org Subject: RE: Bind9 Issue Message-ID: <004a01c35239$f78778d0$0200a8c0@bartxp> In-Reply-To: <20030724223022.GA78422@grimoire.chen.org.nz>
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=20
> specifically=20
> > for the views feature. The DNS machine is my home router and our=20
> > gaming machine is on another network and physically 60=20
> miles away and=20
> > is nat'ed on a lan. The lan the game server is on has it's own DNS=20
> > machine, but is located behind the same public ip.
> >=20
> > I have DNS setup up so that any requests for=20
> www.gameserver.org (name=20
> > different to protect the=20
> ignorant) that come from that lan get the ip=20
> > 192.168.1.20, the machines internal ip. When logged into the game=20
> > server, I can do a dig www.gameserver.org <my DNS ip> and=20
> the correct=20
> > ip comes back. The problem is that When I dig www.gameserver.org=20
> > @<the lan's DNS machine>, it responds with the public ip, not the=20
> > internal and therefore won't work for the lan.
>=20
> You're going to have to show us the named.conf, before anyone=20
> will answer.
> --=20
> Jonathan Chen <jonc@chen.org.nz>
> ----------------------------------------------------------------------
> "Beer. Now there's a temporary solution."
> - Homer Simpson
>=20
named.conf ****************
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.5 2002/02/04 18:24:21 ume
Exp $
//
// Refer to the named.conf(5) and named(8) man pages for details. If
// you are ever going to setup a primary server, make sure you've
// understood the hairy details of how DNS is working. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amount of useless Internet traffic.
acl internals { 192.168.0.0/24; 127.0.0.1; };
acl mis { 216.57.216.55; };
acl dhcp-server { 127.0.0.1; 192.168.0.1; };
options {
directory "/etc/namedb";
forwarders {
4.2.2.4;
4.2.2.5;
4.2.2.6;
};
};
view "internal" {
match-clients { internals; };
recursion yes;
zone "javaweenie.org" {
type master;
file "db.javaweenie.org.internal";
allow-transfer { none; };
allow-update { dhcp-server; };
};
zone "clanbuckbuck.org" {
type master;
file "db.clanbuckbuck.org.external";
allow-transfer { 12.224.183.109; };
};
};
view "mis" {
match-clients { mis; };
recursion no;
zone "clanbuckbuck.org" {
type master;
file "db.clanbuckbuck.org.mis";
allow-transfer { 12.224.183.109; };
};
};
view "external" {
match-clients { any; };
recursion no;
zone "clanbuckbuck.org" {
type master;
file "db.clanbuckbuck.org.external";
allow-transfer { 12.224.183.109; };
};
};
db.clanbuckbuck.org.mis ******************
$TTL 86400
@ IN SOA clanbuckbuck.org. root.clanbuckbuck.org. (
961230 ; Serial
3600 ; Refresh
300 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS ns.clanbuckbuck.org.
IN MX 10 clanbuckbuck.org.
IN A 4.47.114.1
ns IN A 4.47.114.1
=20
www IN A 192.168.1.20
db.clanbuckbuck.org.external ***********************
$TTL 86400
@ IN SOA clanbuckbuck.org. root.clanbuckbuck.org. (
961230 ; Serial
3600 ; Refresh
300 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS ns.clanbuckbuck.org.
IN NS2 ns2.clanbuckbuck.org.
IN MX 10 clanbuckbuck.org.
IN A 4.47.114.1
ns IN A 4.47.114.1
ns2 IN A 12.224.183.109
=20
www IN A 216.57.216.55
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004a01c35239$f78778d0$0200a8c0>