Q: I get "Error 1067" when starting named under Windows.
This commit is contained in:
21
FAQ
21
FAQ
@@ -447,3 +447,24 @@ A: This is usually a configuration error.
|
||||
ensure that /etc/rndc.conf has the correct ownership and that
|
||||
a copy is in the chroot area. You can do this by re-running
|
||||
"rndc-confgen -a" with appropriate -t and -u arguements.
|
||||
|
||||
|
||||
Q: I don't get RRSIG's returned when I use "dig +dnssec".
|
||||
|
||||
A: You need to ensure DNSSEC is enabled (dnssec-enable yes;).
|
||||
|
||||
|
||||
Q: I get "Error 1067" when starting named under Windows.
|
||||
|
||||
A: This is the service manager saying that named exited. You need to
|
||||
examine the Application log in the EventViewer to find out why.
|
||||
|
||||
Common causes are that you failed to create "named.conf" (usually
|
||||
"C:\windows\dns\etc\named.conf") or failed to specify the directory
|
||||
in named.conf.
|
||||
|
||||
options {
|
||||
Directory "C:\windows\dns\etc";
|
||||
};
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user