"private network" vs. DNS/bind config

NetGuy's eMail netguy at northwestcomputer.com
Thu Jul 26 03:35:09 UTC 2001


Dan

The following is what I came up with.  Don't know if it is "the right thing
to do" or not, but it seems to be working.  There are two files, the zone
file and the named.conf file.  This is running on an internal box ( Pent 133
with 40Meg, small HD ) that I have setup as a primary server; bind 8.2.2.P5.
There are some things that probably don't need to be there, and I didn't
show the 127.in-addr.arap zone along with the local host stuff.  As you
probably will guess, .15 and .16 are the slave servers on the internet.
Well, ok so those IP's are the back side of the Internet....  Hope you get
some milage from it!

tod

options {
 directory "/var/named";
 pid-file "/var/named/named.pid";
 named-xfer "/usr/sbin/named-xfer";
 query-source address * port 53;
 notify yes;
 check-names master fail;

 auth-nxdomain yes;

 allow-query     { any; };

 allow-transfer  { 192.168.100.15;
                        192.168.100.16;
 };

 listen-on       { 192.168.100.18;
              127.0.0.1;
 };
};

logging {
 channel Zones {
 file "/var/log/zonexfer.log" versions 3;
 severity info;
 print-category yes;
 print-severity yes;
 print-time yes;
 };

 category xfer-in  { Zones; };
 category xfer-out { Zones; };
 catego6ry notify { Zones; };
};

zone "bind" CHAOS {
 type master;
 file "named.bind";
};

zone "0.0.127.in-addr.arpa" IN {
 type master;
 file "named.127.in-addr.arpa";
};

zone "localhost" IN {
 type master;
 file "named.localhost";
};

zone "everett"  in      {
 type master;
 file "named.everett";
};

zone "100.in-addr.arpa" in      {
 type master;
 file "named.192.168.100.arpa";
};

zone "." {
 type hint;
 file "named.ca";
};

************************************************

$TTL 1D;
everett.     IN     SOA     everett. domadmin.everett. (
                  2001062702 ; serial
                  810800  ; refresh
                  3600  ; retry
                  604800 ; expires
                  86400  ; ttl
  )
everett.       IN      NS ns0.everett.

backside     IN     A     192.168.100.1
rotinom       IN     A     192.168.100.2
retuor216   IN     A     192.168.100.3
flametester  IN     A     192.168.100.4
devious       IN     A     192.168.100.5
verizone      IN     A     192.168.100.6
mocha        IN     A     192.168.100.7
sretupmoc  IN     A     192.168.100.8
masher       IN     A     192.168.100.9
nimrod       IN     A     192.168.100.10
buzzsaw     IN     A     192.168.100.11
molassas    IN     A     192.168.100.12
;notused     IN     A     192.168.100.13
;notused     IN     A     192.168.100.14
ns1            IN     A     192.168.100.15
ns2            IN     A     192.168.100.16
ns0            IN     A     192.168.100.18




"Dan St.André" <dansaintandre at mindspring.com> wrote in message
news:3B5F4724.9D6D9F94 at mindspring.com...
>
> Folks,
>     What are the conventions for DNS names for the hosts of a "private
> network"?
> I do not have a registered domain -- don't need one -- but I used
> sendmail inside my
> firewall and it seems to require a DNS.  I don't want to edit /etc/host
> files around my
> lan.
>
> QUESTION:  When I create a host, say "goofey" on this private network,
> say "192.168.10.0", what do I tell my DNS?
>
> QUESTION:  I can create a bogus domain, say "myplace.lan" and configure
> all of the parts.  My insider hosts can then refer to
> "goofey.myplace.lan".   This mostly works, but is this "the right thing
> to do"?  Is there some other convention?
>
> QUESTION:  Are there other RFC's or HOWTO's that specifically address
> this situation
> in whole or in part?
>
>     I have a lan and a hub.  I follow the rules and use an RFC 1597
> private network for my IP addresses.  I have a caching BIND-8 DNS
> running on my gateway/firewall box.
>
>
>
>

NetGuy aka FlameTester
NorthWestComputer.Com, Inc.
2815 Baker
Everett, Wa 98201

425.252.7498
425.252.7498




More information about the bind-users mailing list