Running an authoritative name server on a small home lan as training
exercise. And using DNS and Bind 4th ed as a guide.
A quick sketch of this network(There are more hosts on it
but for simplicity):
(All have prefix 192.168 and netmask 255.255.255.0)
INTERNET
| (Dynamic IP)
|
NETGEAR (consumer grade router)
reader | 0.20 fwobsd
--------------------------------------------------
| 0.4 | 0.3 | 0.5 | 0.19
| | | |
[ m1 ] [ m2 ] [ m3 ] [ m4 ]
| 1.2 | 1.1
|________________________________________________|
rdmz fwdmz
So I have two networks here.. 192.168.0/24 and 192.168.1/24
M1 and M4 both have 2 nics and addresses in 192.168.0 and 192.168.1
as shown... (if mail doesn't mangle my asci production too bad.)
My problem is how to integrate 192.168.1/24 into my zone.files
The reverse-pointer zone.file for 192.168.1 is where the rub is.
I'm very inexperienced with routing in general and nameservers in
particular .... setting up a home lan nameserver is a training
exercise for me.
Where I get confused is what is the origin `@' for this zone?
Can I use `@' or need to spell out 192.168.1?
What happens to my domain... `local.lan' does it still cover what are
now really two numeric domains 192.168.0 and 192.168.1?
I've tried various combinations in the reverse zone for 192.168.1, but
all I've tried have has one or another problem loading, or being
ignored.
The reverse file for 192.168.1 is below and at the end .. after names
logs is the db.local.lan zone file.
(naming convention stolen from DNS and Bind (4th ed))
I'll post, at the end the named log output from this zone.file as
an example but as mentioned, I've tried quite a few combinations
unsuccessfully. I can post them all but hopefully someone will see
the problem I've created. This one causes the 2 address in 192.168.1
to simply be ignored... other versions have different reasons for not
loading properly.
db.192.168.1
============ 8< snip =================
$TTL 1D
@ IN SOA reader.local.lan. reader.reader.local.lan. (
200405190 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
;
; Name servers (The name '@' is implied)
;
IN NS reader
;
; Addresses point to canonical names
;
192.168.1.2 IN PTR rdmz.local.lan.
192.168.1.1 IN PTR fwdmz.local.lan.
====== 8< snip ===========================
[ -ed leaving `@' as is but spelling out canonical IP for the
two on 192.168.1 cause them to be ignored]
Mar 4 09:59:39 reader named[8959]: pri/db.192.168.1:18: ignoring
out-of-zone data (192.168.1.2)
Mar 4 09:59:39 reader named[8959]: pri/db.192.168.1:19: ignoring
out-of-zone data (192.168.1.1)
Mar 4 09:59:39 reader named[8959]: zone 1.168.192.in-addr.arpa/IN:
loaded serial 200405190
=========== [...] ==========
db.local.lan (I think this is close to right at least)
======== 8< snip ============================
$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
============ 8< snip ==================
--
gentoo-user@gentoo.org mailing list
