Jo Are Rosland <[EMAIL PROTECTED]> writes:
> - Where names are used -- eg. the 'key' field of an 'IN A' entry, or the
> 'value' field of an 'IN PTR' entry -- you may specify the full name by
> ending it with a '.'. Names with no '.' at the end have the origin
> appended.
>
> Now, if you look at your 'IN NS' line (which specifies the authorative name
> server for your reverse domain), it translates into:
>
> <key> <ttl> <class> <type> <value>
> 1.168.192.in-addr.arpa. 1D IN NS reader.1.168.192.in-addr.arpa.
>
> Which is not what you want.
>
> Instead, try the following line:
>
> IN NS reader.local.lan.
I see what you mean. However, I think your response was to the first
example reverse zone posted and not the one that tries to follow
AlexanderK's example. I made the same mistake in the next posted
example and have now corrected that.
> In addition, 'reader' should have an 'IN A' entry in the 'local.lan' zone
> file.
Yes, I've now posted that file too.
But apparently my db.192.168.1 as it now stands still has serious
errors.
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.
=============================================
The above db.192.168.1 is largely rejected (ignored)
Mar 5 07:12:12 reader named[9429]: pri/db.192.168.1:3: ignoring
out-of-zone data (0.168.192.IN-ADDR.ARPA)
Mar 5 07:12:12 reader named[9429]: zone 1.168.192.in-addr.arpa/IN: has
0 SOA records
Mar 5 07:12:12 reader named[9429]: zone 1.168.192.in-addr.arpa/IN: has
no NS records
================================
Changing it to:
$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
Removing the preceeding `@' completely ... it seem then the defined
$ORIGIN would be used.
Gets rejected too:
=====================
Mar 5 07:26:41 reader named[10186]: pri/db.192.168.1:3: no current
owner name
Mar 5 07:26:41 reader named[10186]: zone 1.168.192.in-addr.arpa/IN:
loading master file pri/db.192.168.1: no owner
====================
Trying the full notation then:
$TTL 1D
$ORIGIN 0.168.192.IN-ADDR.ARPA.
lan.local.IN-ADDR.ARPA. IN SOA reader.local.lan. reader.reader.local.lan. (
============================
Mar 5 07:28:41 reader named[10308]: pri/db.192.168.1:3: ignoring
out-of-zone data (lan.local.IN-ADDR.ARPA)
Mar 5 07:28:41 reader named[10308]: zone 1.168.192.in-addr.arpa/IN:
has 0 SOA records
Mar 5 07:28:41 reader named[10308]: zone 1.168.192.in-addr.arpa/IN:
has no NS records
===========================
clearly I'm missing something important here..
--
gentoo-user@gentoo.org mailing list
