On 05.03, Harry Putnam wrote:
>
> Following Alexanders example I tried to redefine $ORIGIN near the top
> since as you point out `@' contains whatever is in named.conf to start.
>
> $TTL 1D
> $ORIGIN 0.168.192.IN-ADDR.ARPA. ;; RESET ORIGIN HERE SO THAT
> ;;THE SOA line won't be rejected for being `out of zone'
> @ 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)
> ;;; $ORIGIN shoud still hold here RIGHT?
> IN NS reader.local.lan. ;; CORRECTED no uses Canonical form
> $ORIGIN 1.168.192.IN-ADDR.ARPA. ;; RESET to handle 192.168.1
> ;
> ; Addresses point to canonical names
> ;
>
> 2 IN PTR rdmz.local.lan.
> 1 IN PTR fwdmz.local.lan.
Hmm. I guess you could try to define the zone 168.192.in-addr.arpa instead.
Then you'd have this in named.conf:
zone "168.192.in-addr.arpa" IN { type master; file "pri/168.192.zone";
notify no; };
And in pri/168.192.zone:
@ 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)
)
IN NS reader.local.lan.
1.0 IN PTR fwdmz.local.lan.
2.0 IN PTR rdmz.local.lan.
1.1 IN PTR a.local.lan. ; whatever: some host name in 192.168.1.0/24
2.1 IN PTR b.local.lan. ; whatever: some host name in 192.168.1.0/24
> $TTL 1D
> $ORIGIN 0.168.192.IN-ADDR.ARPA.
> lan.local.IN-ADDR.ARPA. IN SOA reader.local.lan. reader.reader.local.lan.
> (
This is definitely wrong:
- the 'IN SOA' entry should have the origin as key
- it doesn't make any sense to use anything but reverse IP network addresses off
the in-addr.arpa domain
It should not be necessary to set the $ORIGIN to the same value you defined in
the named.conf file.
If you try to put two zones inside one file, as you do in your reverse zone,
in addition to redefining $ORIGIN, you need to put in an additional 'IN SOA'
entry. I believe the missing 'IN SOA' for your second reverse zone is the
reason bind complains about 'no owner'.
And again: it's really no reason why you can't put all of this into one zone
instead.
--
Jo.
--
gentoo-user@gentoo.org mailing list
