Confused about named.local semantics

[Terry Lee, Publisher]

I realize that my network seems to be working perfectly and that I shouldn't
fix it, but it is driving me crazy which SOA and NS entries are correct for
named.local on primary and secondary name servers for the zone area-net.com
which uses ns1.area-net.com (12.22.230.1) & ns2.area-net.com (12.22.230.2)
for name servers:

IN SOA localhost.
IN NS localhost.

or

IN SOA ns1.area-net.com
IN NS ns1.area-net.com
IN NS ns2.area-net.com


Both examples are found with about equal frequency. The DNS and BIND book
states the latter example, but my RedHat 6.1 distro used the former method
in its initial generic files.

I realize the PTR entry should always reference localhost.


Also, is it not true that on the primary box my resolv.conf should look
like:

search mydomain.com
nameserver 127.0.0.1
nameserver 12.22.230.2

...and that the same file on the secondary(s) should look like:

search mydomain.com
nameserver 12.22.230.1
nameserver 127.0.0.1

and all other non-dns serving boxes:

search mydomain.com
nameserver 12.22.230.1
nameserver 12.22.230.2

Or have I go it all wrong?

Any help would be forever appreciated.


Terry Lee, Publisher
Area-Net, Inc.
magic at nospam.area-net.com