problem with bind 9.0.1
Jason Richards
jrichards at gci.com
Fri Jan 12 18:10:56 UTC 2001
I recently compiled 9.0.1 successfully on Solaris 7, but I did have the same
result as you at first. I found out what was wrong by looking in the
messages log files (/var/adm/messages). It was complaining about my
configuration for various reasons: errors in named.conf seemed to be the
fatal ones. My suggesting to you would be to make sure syslog is logging
all facilities and appropriate severities (since I can't remember the exact
facility.severity that named logs to) and check those log files. If your
problem is anything like mine, then you will find your answer there.
Jason
-----Original Message-----
From: loren jan wilson [mailto:ljwilson at midway.uchicago.edu]
Sent: Friday, January 12, 2001 9:00 AM
To: bind-users at isc.org
Subject: problem with bind 9.0.1
i've compiled bind 9.0.1 on a solaris 7 machine, and when i run it as
"./named -?"
it prints the proper arguments. when i run it as
"./named -c /var/named/named.conf"
it doesn't do anything at all...just quits to the prompt. no core
file. no error messages. nothing.
the named.conf is as sparse as it could get...
options {
directory "/var/named";
};
zone "." {
type hint;
file "named.ca";
};
i also compiled it on my solaris 8 workstation, and got exactly the
same result. what's going on? did i forget something in the compiling
stage? (it was compiled with
./configure --prefix=/opt/pkgs/bind-9.0.1; make; make install
)
thanks,
loren
More information about the bind-users
mailing list