DirectSlave/GO 3 - public beta

bdacus01 said:

General DNS | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com

If you need to transfer all of your zones from your current machine to the servers listed in your MultiServer IP list, then you can type:

Code: 
echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue

which will rewrite all local zones, and thus trigger the transfer of them to the remote servers
Click to expand...
Thanks for the answer.

The domain that I added was after configuring the multi-server setup with directslave.
Thus should this not be needed? (Please correct me if I am wrong.)

The second thing that I notice is that there are no files in /etc/named/secondary/. (Not even named.conf)
But I do have a directslave.inc with the domain name in it that I just added.

And when I run directslave --check Then I get no errors.

So it seems to be not working correctly?
Please advice.
 
bdacus01 said:
only if you have other zones on the primary server

I stoped using this a while back to use PowerDNS. One day I might rewrite my script.
Click to expand...
Thanks.

The only thing that I do not understand is why directslave does not make the zone files for the domains.
It adds the domains to the directslave.inc and links them to a .db file but the .db file is nowhere to be found.
 
in the directslave web gui you added them there?

ports 2222 and 53 all open on the directslave server?
 
bdacus01 said:
in the directslave web gui you added them there?

ports 2222 and 53 all open on the directslave server?
Click to expand...
No I added in my directadmin panel and multi-server added them to the directslave.
And yes port 2222 and port 53 are accessible on both directadmin and directslave.
 
realcryptonight said:
No I added in my directadmin panel and multi-server added them to the directslave.
And yes port 2222 and port 53 are accessible on both directadmin and directslave.
Click to expand...
And the weird thing is that the domain gets added to the directslave.inc but the .db file for that domain never gets made.
 
@cjd I have it almost working.

But do I need to make a named.conf file for bind9? or does directslave do this?
And if I need to make it myself what do I need to put in it?

Sorry if these are noob questions but I am an sysadmin for DirectAdmin and used to DirectAdmin just configuring these things.
 
Last edited:
On direct slave host:

named.conf added:

include "/etc/bind/directslave.inc";

named.conf.options:

allow-query { any; };
allow-notify { ip of DA server; };
allow-transfer { ip of DA server; };
recursion no;

On DA Host:

named.conf.options:

also-notify { ip of Directslave; };
allow-transfer { ip of Directslave; };
notify explicit;
 
cjd said:
On direct slave host:

named.conf added:

include "/etc/bind/directslave.inc";

named.conf.options:

allow-query { any; };
allow-notify { ip of DA server; };
allow-transfer { ip of DA server; };
recursion no;

On DA Host:

named.conf.options:

also-notify { ip of Directslave; };
allow-transfer { ip of Directslave; };
notify explicit;
Click to expand...
Thanks,

But for whatever reason bind9 does not start when I add include "/etc/bind/directslave.inc" to /etc/bind/named.conf
The file itself exists and it has the correct permissions.

Bind9 service output:
root@**myserver**:~# service bind9 status
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-03-26 12:22:25 CDT; 1s ago
Docs: man:named(8)
Process: 12069 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE)
Main PID: 12069 (code=exited, status=1/FAILURE)
CPU: 25ms

Mar 26 12:22:25 **myserver** systemd[1]: named.service: Scheduled restart job, restart count>
Mar 26 12:22:25 **myserver** systemd[1]: Stopped BIND Domain Name Server.
Mar 26 12:22:25 **myserver** systemd[1]: named.service: Start request repeated too quickly.
Mar 26 12:22:25 **myserver** systemd[1]: named.service: Failed with result 'exit-code'.
Mar 26 12:22:25 **myserver** systemd[1]: Failed to start BIND Domain Name Server.
Click to expand...

EDIT:

Forgot to notice/add the ; after "
Now it starts. :)
 
Last edited:
What does the log file say? It should gave some kind of reason. File should be owned root:bind, 644 permissions.

Also, if apparmor is running you will need to add:

/etc/bind/secondary/** rw,

to the /etc/apparmor.d/local/usr.sbin.named

and do a:

service apparmor reload
 
cjd said:
What does the log file say? It should gave some kind of reason. File should be owned root:bind, 644 permissions.

Also, if apparmor is running you will need to add:

/etc/bind/secondary/** rw,

to the /etc/apparmor.d/local/usr.sbin.named

and do a:

service apparmor reload
Click to expand...
The only problem left is: No .db files are created in the secondary folder.
And there is nothing in the log files.

It has permission 755 and is owned by: root:bind for the secondary folder
When I run /usr/local/directslave/bin/directslave --check I get no errrors back.

The bind9 service is running and active on both directadmin and directslave server.
Any ideas?
 
If you have apparomor running you will need to do what I mentioned in my last message so bind can write to the directory.
 
cjd said:
If you have apparomor running you will need to do what I mentioned in my last message so bind can write to the directory.
Click to expand...
I have done that but still no .db files. :(

EDIT:
And yes I did clearout the directslave.inc and run echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue on the directadmin server.
 
Humm have you checked the log files to see if there are any messages?

/var/log/messages
/var/log/syslog
 
cjd said:
Humm have you checked the log files to see if there are any messages?

/var/log/messages
/var/log/syslog
Click to expand...
The only thing I can find that is related to named/bind is:
Mar 26 13:27:18 **myserver** kernel: [103762.802779] audit: type=1400 audit(1648319238.951:158): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="named" pid=13586 comm="apparmor_parser"
 
Just checking. If your directslave.conf you have:

named_workdir /etc/bind/secondary
named_conf /etc/bind/directslave.inc

And reading though the directslave.inc file in the bind directory you should see each line like:

zone "domain.com" { type slave; file "/etc/bind/secondary/domain.com.db"; masters { DA server IP; }; max-retry-time 1200; min-retry-time 1200; masterfile-format text; };
 
cjd said:
Just checking. If your directslave.conf you have:

named_workdir /etc/bind/secondary
named_conf /etc/bind/directslave.inc

And reading though the directslave.inc file in the bind directory you should see each line like:

zone "domain.com" { type slave; file "/etc/bind/secondary/domain.com.db"; masters { DA server IP; }; max-retry-time 1200; min-retry-time 1200; masterfile-format text; };
Click to expand...
Yes, that how I have it. And all the domains are in the directslave.inc file.
I am just missing the .db files in /etc/bind/secondary folder.
 
Humm that's strange. And you did restart apparmor after making the changes? Maybe also restart bind9? Chmod secondary 775?
 
cjd said:
Humm that's strange. And you did restart apparmor after making the changes? Maybe also restart bind9? Chmod secondary 775?
Click to expand...
I restarted apparmor and bind9 just to be safe and changed secondary folder to 775 but still no .db files in the secondary folder.
Even tho the domains are in the directslave.inc
 
Also when I add test.nl as a domain to DA and when its pushed to DS and then delete it again in DA I see this in the error.log
2022/03/26 15:13:21 Cant' delete zone file, /etc/bind/secondary/test.nl.db not found.

But I cannot find any error from when it should have created that file.
 
You must log in or register to reply here.
Back
Top