Add new subnet on multi-homed hosts
Harry Putnam
reader at newsguy.com
Sun Mar 5 08:21:33 UTC 2006
Barry Margolin <barmar at alum.mit.edu> writes:
> We need to see the named.conf file to tell whether you're loading
> db.192.168.1 into the correct zone.
The setup has changed since I posted the previous message but the
problem persists. The current setup consist of 2 subnets
192.168.0/24
192.168.1/24
The diagram for clarity:
(All addresses have prefix 192.168)
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
|__________________ chintzy hub _________________|
rdmz fwdmz
I've added a few things to the diagram to ease conversation.
Machine1 (m1) and Machine4 (m4) are multi-homed .. 2 nics each
Neither has internal forwarding enabled
The second nics are on network 192,168.1/24 ... all others are on
192.168.0/24
m1: m4:
reader 192.168.0.4 fwobsd 192.168.0.19
rdmz 192.168.1.2 fwdmz 192.168.1.1
The second nics are hardwired to each other thru a hub, and are not
connected to anything else.
nslookup finds all alphabetical names and all but the two 192.168.1/24
address numeric IP names So something is wrong with db.192.168.1 for
sure and maybe more. If db.192.168.1 looks kind of beat up, its from
trying to figure out what it needs. In this example it is simply
ignored by named.
named.conf
==================================
options {
directory "/var/bind";
listen-on-v6 { none; };
listen-on { LOCALHOST; };
listen-on { LOCALNETS; };
pid-file "/var/run/named/named.pid";
};
zone "." IN {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "pri/db.127.0.0";
allow-update { none; };
notify no;
};
//# [HP 01/29/06 08:11 My additions below here]
zone "local.lan" IN {
type master;
file "pri/db.local.lan";
};
zone "0.168.192.in-addr.arpa" IN {
type master;
file "pri/db.192.168.0";
};
zone "1.168.192.in-addr.arpa" IN {
type master;
file "pri/db.192.168.1";
};
========================
db.local.lan
=======================
$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
db.192.168.0
========================
$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.local.lan.
;
; Addresses point to canonical names
;
3 IN PTR mob2.local.lan.
4 IN PTR reader.local.lan.
16 IN PTR bjp.local.lan.
19 IN PTR fwobsd.local.lan.
20 IN PTR fw.local.lan.
21 IN PTR ansil.local.lan.
22 IN PTR harvey.local.lan.
50 IN PTR wap.local.lan.
db.192.168.1
===========================
$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.
More information about the bind-users
mailing list