-- SLAVE DNS SOLUTION --
Solution to Secondary DNS Issue:
Dear DA Community:
I purchased my first DA license last night and have been busy configuring/securing it. I have also been reading all the interesting suggestions and solutions that various members of the community have put forward. But here is what I suggest and I believe it should be very simple to implement and if my shell-scripting knowledge didn't let me down, I would have done it in a few hours:
I have tested this on RedHat EL 3 and it works and I don't see why it shouldn't on other *nix environment
OK here it goes:
1- DIRECTADMIN is the primary Name Server
2- Consider an arbitrary Linux-box/VDS/whatever as the slave DNS.
Configure it so that named.conf and the "slaves" directory are in an isolated area on its harddisk.
You can call it /slaveconfdir/
(so it will contain named.conf file and the "slaves" subfolder.
3- NFS Export "slaveconfdir" to the DIRECTADMIN server and NFS mount it , say in
/mnt/slaveconfdir
By now I hope you know where I'm getting at.
4- All the DA script needs to do now is to add
zone "example.com" {
type slave;
file "/slaveconfdir/slaves/example.com.db";
masters {
ip.add.of.directadmin_server;
};
};
to named.conf on the mounted "slaveconfdir" directory hence writing directly to the configuration file of the slave server
I manually did this and the "slaves" directory was populated after bind was reloaded on the slave box. A cron job can do this periodically
I really wish I was better at shell scripting so that I could implement this today so that a script closely linked to DA's scripts would make sure that the entry is removed from the "slave server's conf file"/"slaves"directory if it's no longer required.
I'd sure appreciate it if anyone could help me out with this.
This is really getting me down.
DA is brilliant but lack of this feature is a real let-down. And as you can see it's really simple to implement.
Solution to Secondary DNS Issue:
Dear DA Community:
I purchased my first DA license last night and have been busy configuring/securing it. I have also been reading all the interesting suggestions and solutions that various members of the community have put forward. But here is what I suggest and I believe it should be very simple to implement and if my shell-scripting knowledge didn't let me down, I would have done it in a few hours:
I have tested this on RedHat EL 3 and it works and I don't see why it shouldn't on other *nix environment
OK here it goes:
1- DIRECTADMIN is the primary Name Server
2- Consider an arbitrary Linux-box/VDS/whatever as the slave DNS.
Configure it so that named.conf and the "slaves" directory are in an isolated area on its harddisk.
You can call it /slaveconfdir/
(so it will contain named.conf file and the "slaves" subfolder.
3- NFS Export "slaveconfdir" to the DIRECTADMIN server and NFS mount it , say in
/mnt/slaveconfdir
By now I hope you know where I'm getting at.
4- All the DA script needs to do now is to add
zone "example.com" {
type slave;
file "/slaveconfdir/slaves/example.com.db";
masters {
ip.add.of.directadmin_server;
};
};
to named.conf on the mounted "slaveconfdir" directory hence writing directly to the configuration file of the slave server
I manually did this and the "slaves" directory was populated after bind was reloaded on the slave box. A cron job can do this periodically
I really wish I was better at shell scripting so that I could implement this today so that a script closely linked to DA's scripts would make sure that the entry is removed from the "slave server's conf file"/"slaves"directory if it's no longer required.
I'd sure appreciate it if anyone could help me out with this.
This is really getting me down.
DA is brilliant but lack of this feature is a real let-down. And as you can see it's really simple to implement.
Last edited: