Bind9 Issue

Derrick Ryalls ryallsd at datasphereweb.com
Thu Jul 24 16:19:08 PDT 2003


> 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 at chen.org.nz>
> ----------------------------------------------------------------------
>                              "Beer. Now there's a temporary solution."
>                                                        - Homer Simpson
> 

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
    
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
    
www	IN      A       216.57.216.55




More information about the freebsd-questions mailing list