Alexander Kirillov <[EMAIL PROTECTED]> writes: >>>What's in your named.conf? >>>Should be something like this: >> Just posted a few minutes ago... but I noticed I wasn't really >> following your example thoroughly. Now trying this db.192.168.1 >> Still fails miserably: >> $TTL 1D >> $ORIGIN 168.192.IN-ADDR.ARPA. >> 0 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 0.168.192.IN-ADDR.ARPA. >> ; >> 4 IN NS reader.local.lan. > > You don't need 4 at the start of the line > >> $ORIGIN 1.168.192.IN-ADDR.ARPA. >> ; >> ; Addresses point to canonical names >> ; >> 2 IN PTR rdmz.local.lan. >> 1 IN PTR fwdmz.local.lan. >> ======= 8< snip =================== >> Produces theses log lines: >> Mar 5 07:35:06 reader named[10615]: pri/db.192.168.1:3: ignoring >> out-of-zone data (0.168.192.IN-ADDR.ARPA) >> Mar 5 07:35:06 reader named[10615]: pri/db.192.168.1:14: ignoring >> out-of-zone data (4.0.168.192.IN-ADDR.ARPA) >> Mar 5 07:35:06 reader named[10615]: zone >> 1.168.192.in-addr.arpa/IN: >> has 0 SOA records >> Mar 5 07:35:06 reader named[10615]: zone >> 1.168.192.in-addr.arpa/IN: >> has no NS records > > Make it 2 separate files for each of the reverse zones. > Each with its own SOA record. > Emerge bind with doc flag and read into Adminstrators Reference Manual
What is the significance of the zero here: >> $ORIGIN 168.192.IN-ADDR.ARPA. >> 0 IN SOA reader.local.lan. reader.reader.local.lan. ( ^^^ -- gentoo-user@gentoo.org mailing list
