Slava Voronin (svevor@home.com)
Wed, 21 Oct 1998 18:23:12 -0700
Ian Dobson wrote:
> using named (bind8) on a linux firewall, and basically it works ok..
> But
> what do I need to add to allow the inside IP's to resolve each others
> names, and so the outside (internet side) can't see them?
>
>
For this purpose I am runing primary and slave dns serveces they
Slave transforms information from primary. Each time when you
do changes on your primary databes do not forget change increment number
.
For primary /etc/resolv.conf
search ml.org
nameserver 0.0.0.0
For slave (in third edition dns books they call secondary as slave)
/etc/resolv.conf
search ml.org
nameserver 24.113.3.19
nameserver 127.0.0.1
to check if you can resolve
to check how nslookup works
vcnet:~# nslookup vcnet.ml.org
Server: vcnet
Address: 0.0.0.0
Name: vcnet.ml.org
Addresses: 24.113.3.19, 192.168.1.1, 192.168.3.1
vcnet:~# nslookup lana.ml.org
Server: vcnet
Address: 0.0.0.0
Name: lana.ml.org
Addresses: 192.168.2.2, 192.168.1.2
vcnet:~# nslookup ntws
Server: vcnet
Address: 0.0.0.0
Name: ntws.ml.org
Addresses: 192.168.3.3, 192.168.2.3
And of course you can resolve any internet address
vcnet:~# nslookup www.cnn.com
Server: vcnet
Address: 0.0.0.0
Name: cnn.com
Addresses: 207.25.71.25, 207.25.71.26, 207.25.71.27, 207.25.71.28
207.25.71.29, 207.25.71.20, 207.25.71.30, 207.25.71.22,
207.25.71.23
207.25.71.24
Aliases: www.cnn.com
you can do resolve of any local and external computer from any internal
computer.
Of course this information not enough. I would recommend O'Reilly third
edition
bind 8. Most comprehensive I've ever seen.
This archive was generated by hypermail 2.0b3 on Mon 02 Nov 1998 - 03:23:18 PST