how to describe subdomains

tony_barratt at my-deja.com tony_barratt at my-deja.com
Tue Nov 9 18:10:57 UTC 1999


Thanx Joe,
I'm taking your advice and making separate zone files, and as I'm
running BIND 4.9 I've tried to put the relevant info in the named.boot
file, and db.ran (+db.212.41.149) and db.rtd01 (+db.212.41.152), but
I'm missing something, I think.

Like so:

bash# cat named.boot
directory /dns/newer
primary 0.0.127.IN-ADDR.ARPA db.127.0.0
primary ran db.ran
primary 149.41.212.IN-ADDR.ARPA db.212.41.149
primary rtd01.ran db.rtd01
primary 152.41.212.IN-ADDR.ARPA db.212.41.152

bash# head db.ran
@ IN  SOA nms01.ran. root.nms01.ran. ( 2 10800 3600 604800 86400 )
  IN  NS  nms01.ran.
  rtd01 IN  NS  nms01.asd04.ran.

localhost            IN  A     127.0.0.1
ws01                 IN  A     212.41.149.138
ws01                 IN  MX    10 ws01.ran.
nms01                IN  A     212.41.149.130
nms01                IN  MX    10 nms01.ran.
$INCLUDE db.rtd01

bash# head db.rtd01
@ IN  SOA nms01.rtd01.ran. root.nms01.rtd01.ran. ( 4 10800 3600 604800
86400 )
  IN  NS  nms01.rtd01.ran.

localhost            IN  A     127.0.0.1
grf01                IN  A     212.41.152.120
rtr08                IN  A     212.41.152.103
rtr09                IN  A     212.41.152.104

bash#      head db.212.41.152
@ IN  SOA nms01.rtd01.ran. root.nms01.rtd01.ran. ( 3 10800 3600 604800
86400 )
  IN  NS  nms01.rtd01.ran.

1.152.41.212.IN-ADDR.ARPA.      IN  PTR   tnt01.rtd01.ran.
2.152.41.212.IN-ADDR.ARPA.      IN  PTR   tnt02.rtd01.ran.
95.152.41.212.IN-ADDR.ARPA.     IN  PTR   tnt95.rtd01.ran.
96.152.41.212.IN-ADDR.ARPA.     IN  PTR   rtr01.rtd01.ran.
99.152.41.212.IN-ADDR.ARPA.     IN  PTR   rtr04.rtd01.ran.
100.152.41.212.IN-ADDR.ARPA.    IN  PTR   rtr05.rtd01.ran.
101.152.41.212.IN-ADDR.ARPA.    IN  PTR   rtr06..rtd01.ran.
bash# cat db.212.41.149
@ IN  SOA nms01.ran. root.nms01.ran. ( 4 10800 3600 604800 86400 )
  IN  NS  nms01.ran.

130.149.41.212.IN-ADDR.ARPA.    IN  PTR   nms01.ran.
138.149.41.212.IN-ADDR.ARPA.    IN  PTR   ws01.ran.

bash# nslookup
Default Server:  nms01.asd04.ran
Address:  212.41.149.130
> 212.41.149.138
Server:  nms01.asd04.ran
Address:  212.41.149.130
<so far so good>
Name:    ws01.asd04.ran
Address:  212.41.149.138

> 212.41.152.1
Server:  nms01.asd04.ran
Address:  212.41.149.130

*** nms01.asd04.ran can't find 212.41.152.1: Server failed
<oh dear!>

any suggestions welcome..

TIA

Tony
In article <199911082227.RAA04328 at fw1-a.osis.gov>,
  Joseph S D Yao <jsdy at cospo.osis.gov> wrote:
> > Hi List,
> > I'm setting up a private DNS server for the domain ran, which has,
> > asd01, asd02.., asd0n as subdomains. So anyhow I have generated a
file
> > db.ran which has a SOA that sez this file is authorative for ran.
> > But how do I specify the subdomains asd01 etc? All the examples I've
> > seen assume that the subdomain are defined on a different server not
> > the same one.
> > Well that's no quite true I've seen one (ie a db.domainname file)
that
> > has
> > $INCLUDE db.subdomain1.domainname
> > $INCLUDE db.subdomain2.domainname
> > ...
> > $INCLUDE db.subdomainx.domainname
> > which seems to work.
> > Is there, however, a more sensible approach?
>
> You may put it all in one file, although I wouldn't:
>
> name1.asd01	IN	A	...
> name2.sad01	IN	A	...
> ...
> name1.asd02	IN	A	...
> name2.asd02	IN	A	...
> ...
>
> Or you may make separate zone files for each zone on the same server:
>
> db.ran:
> $TTL		1d
> @	IN SOA	... (...)
> 	IN NS	ns.ran
>
> asd01	IN NS	ns.ran
> asd02	IN NS	ns.ran
> ...
>
> And then, in your named.conf file, you would have to declare these as
> separate zones, with the names of their zone files, etc.
>
> If you are running an old, old BIND 4, you would do the same thing in
> the named.boot file.  The zone files haven't changed much, except that
> you used to be able to confuse yourself by having multiple unrelated
> domains in the same zone file.  ;-]
>
> --
> Joe Yao				jsdy at cospo.osis.gov - Joseph S.
D. Yao
> COSPO/OSIS Computer Support					EMT-B
>
-----------------------------------------------------------------------
>       This message is not an official statement of COSPO policies.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.


More information about the bind-users mailing list