On 04.03, Harry Putnam wrote: > > $TTL 1D > @ IN SOA reader.local.lan. hostmaster ( > 200405191 ; serial > 8H ; refresh > 4H ; retry > 4W ; expire > 1D ) ; minimum > ;; Nameserver (The name '@' is implied) > IN NS reader > ;; smtp hub (The name '@' is implied) > IN MX 10 reader > ;; addresses for the canonical names > localhost IN A 127.0.0.1 > ansil IN A 192.168.0.21 > bjp IN A 192.168.0.16 > fw IN A 192.168.0.20 > fwobsd IN A 192.168.0.19 > IN A 192.168.1.1 > harvey IN A 192.168.0.22 > mob2 IN A 192.168.0.3 > reader IN A 192.168.0.4 > IN A 192.168.1.2 > wap IN A 192.168.0.50 > > ;; aliases > smtp IN CNAME reader > www IN CNAME reader > tic IN CNAME reader > > ;; interface specific addresses > fwdmz IN A 192.168.1.1 > rdmz IN A 192.168.1.2
Just a few additional comments on this: Your entries for 'reader' and 'fwobsd' are probably not what you really want. By defining several 'IN A' entries for the same host name, you effectively get bind to serve these addresses in 'round robin' fashion whenever a client looks up that name. Another way to look at this is that you don't name hosts in DNS, you name IP addresses. If a host has several IP addresses, eg. because it has several NIC's, you should give a separate name to each IP address. In your case, you could do something like this: reader IN A 192.168.0.4 reader0 IN A 192.168.0.4 reader1 IN A 192.168.1.2 or reader0 IN A 192.168.0.4 reader1 IN A 192.168.1.2 reader IN CNAME reader0 Note that you may define as many names for an IP address as you like. A case where you'd definitely want to do this, is with the name for the name server host itself. Put in something like this: ns IN A 192.168.0.4 Then you may use 'ns.local.lan.' in all your 'IN SOA' entries instead of the name for the actual host. Then you only need to change one entry in case you want to change to another name server host. Also, note that this has to be an 'IN A' entrym not an 'IN CNAME' entry, as the name in the SOA has to be an 'IN A' entry. -- Jo.
pgpWctwjUd1k4.pgp
Description: PGP signature
