1 |
Running an authoritative name server on a small home lan as training |
2 |
exercise. And using DNS and Bind 4th ed as a guide. |
3 |
|
4 |
A quick sketch of this network(There are more hosts on it |
5 |
but for simplicity): |
6 |
|
7 |
(All have prefix 192.168 and netmask 255.255.255.0) |
8 |
|
9 |
INTERNET |
10 |
| (Dynamic IP) |
11 |
| |
12 |
NETGEAR (consumer grade router) |
13 |
reader | 0.20 fwobsd |
14 |
-------------------------------------------------- |
15 |
| 0.4 | 0.3 | 0.5 | 0.19 |
16 |
| | | | |
17 |
[ m1 ] [ m2 ] [ m3 ] [ m4 ] |
18 |
| 1.2 | 1.1 |
19 |
|________________________________________________| |
20 |
rdmz fwdmz |
21 |
|
22 |
So I have two networks here.. 192.168.0/24 and 192.168.1/24 |
23 |
M1 and M4 both have 2 nics and addresses in 192.168.0 and 192.168.1 |
24 |
as shown... (if mail doesn't mangle my asci production too bad.) |
25 |
|
26 |
My problem is how to integrate 192.168.1/24 into my zone.files |
27 |
|
28 |
The reverse-pointer zone.file for 192.168.1 is where the rub is. |
29 |
I'm very inexperienced with routing in general and nameservers in |
30 |
particular .... setting up a home lan nameserver is a training |
31 |
exercise for me. |
32 |
|
33 |
Where I get confused is what is the origin `@' for this zone? |
34 |
Can I use `@' or need to spell out 192.168.1? |
35 |
What happens to my domain... `local.lan' does it still cover what are |
36 |
now really two numeric domains 192.168.0 and 192.168.1? |
37 |
|
38 |
I've tried various combinations in the reverse zone for 192.168.1, but |
39 |
all I've tried have has one or another problem loading, or being |
40 |
ignored. |
41 |
|
42 |
The reverse file for 192.168.1 is below and at the end .. after names |
43 |
logs is the db.local.lan zone file. |
44 |
|
45 |
(naming convention stolen from DNS and Bind (4th ed)) |
46 |
|
47 |
I'll post, at the end the named log output from this zone.file as |
48 |
an example but as mentioned, I've tried quite a few combinations |
49 |
unsuccessfully. I can post them all but hopefully someone will see |
50 |
the problem I've created. This one causes the 2 address in 192.168.1 |
51 |
to simply be ignored... other versions have different reasons for not |
52 |
loading properly. |
53 |
|
54 |
db.192.168.1 |
55 |
============ 8< snip ================= |
56 |
$TTL 1D |
57 |
@ IN SOA reader.local.lan. reader.reader.local.lan. ( |
58 |
200405190 ; serial |
59 |
28800 ; refresh (8 hours) |
60 |
14400 ; retry (4 hours) |
61 |
2419200 ; expire (4 weeks) |
62 |
86400 ; minimum (1 day) |
63 |
) |
64 |
; |
65 |
; Name servers (The name '@' is implied) |
66 |
; |
67 |
IN NS reader |
68 |
; |
69 |
; Addresses point to canonical names |
70 |
; |
71 |
|
72 |
192.168.1.2 IN PTR rdmz.local.lan. |
73 |
192.168.1.1 IN PTR fwdmz.local.lan. |
74 |
|
75 |
====== 8< snip =========================== |
76 |
|
77 |
[ -ed leaving `@' as is but spelling out canonical IP for the |
78 |
two on 192.168.1 cause them to be ignored] |
79 |
|
80 |
Mar 4 09:59:39 reader named[8959]: pri/db.192.168.1:18: ignoring |
81 |
out-of-zone data (192.168.1.2) |
82 |
Mar 4 09:59:39 reader named[8959]: pri/db.192.168.1:19: ignoring |
83 |
out-of-zone data (192.168.1.1) |
84 |
Mar 4 09:59:39 reader named[8959]: zone 1.168.192.in-addr.arpa/IN: |
85 |
loaded serial 200405190 |
86 |
|
87 |
=========== [...] ========== |
88 |
|
89 |
db.local.lan (I think this is close to right at least) |
90 |
======== 8< snip ============================ |
91 |
$TTL 1D |
92 |
@ IN SOA reader.local.lan. hostmaster ( |
93 |
200405191 ; serial |
94 |
8H ; refresh |
95 |
4H ; retry |
96 |
4W ; expire |
97 |
1D ) ; minimum |
98 |
;; Nameserver (The name '@' is implied) |
99 |
IN NS reader |
100 |
;; smtp hub (The name '@' is implied) |
101 |
IN MX 10 reader |
102 |
;; addresses for the canonical names |
103 |
localhost IN A 127.0.0.1 |
104 |
ansil IN A 192.168.0.21 |
105 |
bjp IN A 192.168.0.16 |
106 |
fw IN A 192.168.0.20 |
107 |
fwobsd IN A 192.168.0.19 |
108 |
IN A 192.168.1.1 |
109 |
harvey IN A 192.168.0.22 |
110 |
mob2 IN A 192.168.0.3 |
111 |
reader IN A 192.168.0.4 |
112 |
IN A 192.168.1.2 |
113 |
wap IN A 192.168.0.50 |
114 |
|
115 |
;; aliases |
116 |
smtp IN CNAME reader |
117 |
www IN CNAME reader |
118 |
tic IN CNAME reader |
119 |
|
120 |
;; interface specific addresses |
121 |
fwdmz IN A 192.168.1.1 |
122 |
rdmz IN A 192.168.1.2 |
123 |
|
124 |
============ 8< snip ================== |
125 |
|
126 |
-- |
127 |
gentoo-user@g.o mailing list |