After you have configured the zone, the data is available to any of the Novell DNS servers you select to make authoritative for the zone.The Novell DNS server takes advantage of the peer-to-peer nature of e Directory by replicating the DNS data.
The format and meaning of these messages is specified in RFC 2136. Updating of secure zones (zones using DNSSEC) follows RFC 3007: RRSIG, NSEC and NSEC3 records affected by updates are automatically regenerated by the server using an online zone key.
The journal file is in a binary format and should not be edited manually.
The server will also occasionally write ("dump") the complete contents of the updated zone to its zone file.
Install packages: Then edit /etc/file acl “allowed” ; options ; logging ; zone “.” IN ; include “/etc/named.rfc1912.zones”; include “/etc/key”; zone “122.168.192.in-addr.arpa” IN ; zone “example.com” IN ; check config files for typo errors: of course,at this moment it’ll throw errors that files and reverse.db cannot be found,they don’t exist (yet). Template zone file is located at /usr/share/doc/bind-9.9.4/sample/var/named/named.localhost we can use it as a template for our zone files.
Copy that file to /var/named/chroot/etc/named/ and save as db open db file in your favorite text editor and start editing: @ IN SOA server1. ( 2015052601 ; serial 1D ; refresh 1H ; retry 1W ; expire 3H ) ; minimum @ IN NS server1.