If you are running on a closed network, that should be sufficient (although you still need to add actual A records to your zone file for anything to resolve).
For recursion (using this nameserver to resolve anything other than your .cad), you should define a hints file at a minimum. Here's a typical starting point (stolen from a redhat box) for your named.conf for an internet connected DNS server (on most packaged Bind installations these files referenced should exist, but if they don't they are pretty easy to get or generate, for example, the hints file can be downloaded from www .internic.net/zones/named.root .. just remove the space):
Code:
// generated by named-bootconf.pl
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
include "/etc/rndc.key";
The Zone file looks like:
cad. IN SOA dns1.mydomain.com. postmaster.mydomain.com. (
2006014006; serial
86400; refresh in secs
1800; retry in secs
604800; expire in secs
43200; minimum in secs
)
mysite.cad. 43200 NS ns2.dotster.net.
yoursitename.cad. 43200 NS ns2.dotster.net.
Just a note on serial numbers. While it's not required, the typical format of the serial number for easy updates is YYYYMMDDVV, where YYYY = 4 digit year, MM = 2 digit month, DD = 2 digit day, and VV = 2 digit version (for multiple updates within a single day). Helps guarantee that whenever you do an update, the number is always increased properly.
Bookmarks