Hi, On Mon, 9 Nov 1998, Joakim Schramm wrote:
Graham Murray wrote:
Joakim Schramm <josch57@geocities.com> writes:
I try to set up the Bind8 DNS server, have used the basic named file named.conf in the /bind dir and copied it to /etc/named.conf, set start named to "yes", but at start I just got a message: user "named" unknown
What I did was to use YaST to create a new user & Group called named. -
Yes, that worked, but... should it realy be like this? isn't it a signal that something is wrong somewere, structural or so? Before doing so I tried to do $ ndc start and that starts the server, but rebooting and have the boot up script stating it results in a: user "named" unknown error message, as well as: group "named" unknown if just a user "named" is added. Adding a group "named" as well clears the errmess and starts server at boot...
I just can't see any (logical) reason to why there should need to be a user and group "named" to this to happen. Somewhere something must be "logical" wrong in the script setup, or is I just too newbie to understand this? I want to have a DNS I can trust in and not causing me trouble later on...
Although I do not have any experience with DNS, I suspect that the server attempts to switch to this certain User ID when it is started. Of course, this UID and GID should exist. The installation notes should explain how to correctly set up this user. AFAIK, the user's homedirectory should be "/var/named", the login-shell should be "/bin/false". At least this is how we set it up... No offense, but IMHO I wouldn't mess with critical services like DNS, if I do not fully understand what I am doing... ;-) Bye, LenZ ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e