Some functionality of the server's DNS is only available via manual edits. The problem with this is that any attempt to return to Server Admin management can result in whole thing going fubar.
If you need to get back to a 'clean' DNS, the default files for Tiger Server are here...
10.4 Server Default DNS files...
Clicking on the links should just display the file contents in your browser. To download, ctrl-click and 'save linked file'.
Permissions/ownership...
-rw-r--r-- 1 root wheel 1096 Sep 17 2004 /etc/named.conf
-rw-r--r-- 1 root wheel 211 Sep 17 2004 /var/named/localhost.zone
-rw-r--r-- 1 root wheel 2769 Sep 17 2004 /var/named/named.ca
-rw-r--r-- 1 root wheel 230 Sep 17 2004 /var/named/named.local
Named.conf is the prime candidate to turn itself inside out. The following is the full default text for this file...
// Declares control channels to be used by the rndc utility.
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
//
controls {
inet 127.0.0.1 port 54 allow {any; };
};
options {
directory "/var/named";
allow-transfer {none;};
recursion true;
/*
* 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
//
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; };
};
logging {
channel _default_log {
file "/Library/Logs/named.log";
severity info;
print-time yes;
};
category default {
_default_log;
};
};
Comments