DA without named

Redevelopment

Redevelopment

Verified User
Joined
Dec 8, 2004
Messages
53
Location
The Netherlands
Hi all,

Is it possible to tell DA to stop using named. I didn't install BIND and stopped it in the service monitor. I also tried commenting out the lines concerning named in directadmin.conf, but to no avail;
I still get error messages that DA is unable to create a zonefile when I create a new domain and it also keeps complaining that named can't be started in the messagesystem.

The thing is that I really don't need to run BIND on this server, because I already have two nameservers which I can control from a webbased interface. So is it possible to run DA without using a named daemon?
 
I have been long waiting hoping for DA to add an option to remove the reliance of a zonefile to make an account.
 
I followed the instructions from the Knowledge Base, but it didn't work for me.
I still get the same error when creating a domain:
==============================
Details


Unix User created successfully
User's data directory created successfully
Domains directory created successfully
Domains directory created successfully in user's home


Could not include domain's zone to the

Error Creating Domain

==============================

I also tried creating an empty /var/named, cause I figured DA tries to write its zonefiles there, but that doesn't help either.

I also set "Name server 1" and "Name server 2" to the actual nameservers in the Reseller panel.

Any other ideas or do I just have to live with the errormessage?
 
Why should you have had to create an empty /var/named; shouldn't it have been there already?

If you're running FreeBSD the server may be looking elsewhere; I'm not sure.

If you're running Linux, /var/named should be owned by named:named and should be chmodded 755.

Jeff
 
seems a messy approach, I am sure it wouldnt be too hard to stop DA to even try to make zonefiles and bypass named stuff altogether.
 
jlasman said:
Why should you have had to create an empty /var/named; shouldn't it have been there already?
Click to expand...

No, that's because I don't have BIND installed.


If you're running FreeBSD the server may be looking elsewhere; I'm not sure.

If you're running Linux, /var/named should be owned by named:named and should be chmodded 755.
Click to expand...

The rights are set to 755 already and since I don't have BIND installed I don't have a user and group 'named', therefore the directory is root:root.

I did try it with BIND installed though, but that didn't change anything either.
 
Chrysalis said:
seems a messy approach, I am sure it wouldnt be too hard to stop DA to even try to make zonefiles and bypass named stuff altogether.
Click to expand...

I'd think setting named=OFF in services.status would be enough but it obviously isn't.
 
Redevelopment said:
The rights are set to 755 already and since I don't have BIND installed I don't have a user and group 'named', therefore the directory is root:root.
Click to expand...
Which is why DA can't write to it.

Create a user "named" and a group "named" (we use /bin/false for the login shell) and set the ownership to named:named.

Don't forget to create a shell /etc/named.conf file (probably not the right location if you're running FreeBSD), as well.

Then DA should start working without the error.

Jeff
 
Okay I feel pretty silly about this, but I found out what it was. John suggested the same as you did, so I rechecked everything and found out that I still had the namedconfig= and nameddir= lines commented out in directadmin.conf.

After uncommenting those and restarting directadmin it worked fine.
:rolleyes:
 
You must log in or register to reply here.
Back
Top