Next Big Thing?
- Thread starter rldev
- Start date
fusionictnl
Verified User
Their spending your money 
Just kidding!
Just kidding!
- Joined
- Feb 27, 2003
- Messages
- 8,509
Yes, dns clustering is new major feature for 1.25.0 
We've left it very "open" so that admins can work on either end of the connection to even let apache (or anything that can duplicate the commands) handle the dns on the other end if they want, so they don't need to have 2 DA machines.
The control functions are listed so they can be duplicated in script form if a 2nd DA machine isn't available.
The feature also lets admins ensure that a domain created on one box won't exist on another machine (independant of the dns clustering, but uses the same tools).
More info here:
http://www.directadmin.com/features.php?id=533
Screenshot attached.
John
We've left it very "open" so that admins can work on either end of the connection to even let apache (or anything that can duplicate the commands) handle the dns on the other end if they want, so they don't need to have 2 DA machines.
The control functions are listed so they can be duplicated in script form if a 2nd DA machine isn't available.
The feature also lets admins ensure that a domain created on one box won't exist on another machine (independant of the dns clustering, but uses the same tools).
More info here:
http://www.directadmin.com/features.php?id=533
Screenshot attached.
John
Attachments
hostpc.com
Verified User
John.... will you marry me?? 
Do you have an anticipated release date for this yet?
Dare we dream on Jail ssh?
Do you have an anticipated release date for this yet?
Dare we dream on Jail ssh?
DirectAdmin Support said:Yes, dns clustering is new major feature for 1.25.0
....
The feature also lets admins ensure that a domain created on one box won't exist on another machine (independant of the dns clustering, but uses the same tools).
....
John
Hi John,
This is indeed great news but Jeff and I have been working hard to solve the duplicate zone problem, does this solution check to see if duplicate zones exist? If duplicate zones do exist what does the system do? This is a major issue because I've noticed that even with the best intentions in the world it can happen that you move accounts to a different server and forget to remove it from the first server.
regards,
Onno
- Joined
- Feb 27, 2003
- Messages
- 8,509
If the option is enabled, DA will search that server to see if the zone exists. If it does, it will give the "domain exists" message as if the zone existed on the current machine, preventing the user from creating the domain, or you from creating the user.
If you move accounts to a different machine, then you'd need to make sure that the option is not checked during creation (on machines that share the NS), or if it's the machine that is holding the duplicate, then you'd need to make sure the zone isn't on that machine. If you first delete the account from the server you're moving from, then there won't be any issues (understandably, not always an option).
The checker can only go so far, and it becomes a balance between
1) preventing users on other machines from creating duplicate domains your duplicate zones.
and
2) allowing you to move accounts around.
The "checkbox" should be the balance for you. If you want to flexibility, just uncheck it, and DA will blindly write to other machines, so your zones get duplicates correctly.
I'd recommend keeping the both checked, or none at all during normal operations. When moving accounts, I'd recommend keeping them both unchecked. Once the move is done (assuming users didn't conflict with any zones locally), then you can re-check them, and issue a full rewrite of all dns zone (echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue) and DA will at then transfer everything over.
We may need to add a "remove all zones" button, so DA will remove zones from a remote server. Once complete, you can add them again. We'll see what's needed in upcoming releases.
Thanks for the angle though
John
If you move accounts to a different machine, then you'd need to make sure that the option is not checked during creation (on machines that share the NS), or if it's the machine that is holding the duplicate, then you'd need to make sure the zone isn't on that machine. If you first delete the account from the server you're moving from, then there won't be any issues (understandably, not always an option).
The checker can only go so far, and it becomes a balance between
1) preventing users on other machines from creating duplicate domains your duplicate zones.
and
2) allowing you to move accounts around.
The "checkbox" should be the balance for you. If you want to flexibility, just uncheck it, and DA will blindly write to other machines, so your zones get duplicates correctly.
I'd recommend keeping the both checked, or none at all during normal operations. When moving accounts, I'd recommend keeping them both unchecked. Once the move is done (assuming users didn't conflict with any zones locally), then you can re-check them, and issue a full rewrite of all dns zone (echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue) and DA will at then transfer everything over.
We may need to add a "remove all zones" button, so DA will remove zones from a remote server. Once complete, you can add them again. We'll see what's needed in upcoming releases.
Thanks for the angle though
John
nobaloney
NoBaloney Internet Svcs - In Memoriam †
It's critical that duplicates not be allowed to be created because bind will fail.
The way we've resolved it is that if a duplicate exists the administrator asking for the domain to be created will get a notification, and the duplicate will not be created.
You're to look at and/or use our code; we've made it open source.
Jeff
The way we've resolved it is that if a duplicate exists the administrator asking for the domain to be created will get a notification, and the duplicate will not be created.
You're to look at and/or use our code; we've made it open source.
Jeff
- Joined
- Feb 27, 2003
- Messages
- 8,509
Hello,
A duplicate zone will not be able to exist in one named.conf, no worries about that, it won't happen.
When I said duplicate in my previous post, I was referring to making a copy of the zone on a different server
There is no "off" per domain. If there are enough requests, I can add a "skip list" type feature, where a domain can be added to it, and the domain isn't transferred.
John
A duplicate zone will not be able to exist in one named.conf, no worries about that, it won't happen.
When I said duplicate in my previous post, I was referring to making a copy of the zone on a different server
There is no "off" per domain. If there are enough requests, I can add a "skip list" type feature, where a domain can be added to it, and the domain isn't transferred.
John
Well it will be needed, because I have resellers and normal user's.
The user's are slaved on another box that runs DA so the cluster function is excellent, but I cant use it if its going to be enabled for the resellers that use their own nameserver's. You see the problem here? There must be a few out there who have the same situation.
The user's are slaved on another box that runs DA so the cluster function is excellent, but I cant use it if its going to be enabled for the resellers that use their own nameserver's. You see the problem here? There must be a few out there who have the same situation.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Chrysalis,
Why would it hurt if you end up slaving some domains and you never get a request for them?
Then your only resource "cost" would be the space it takes on your server for the zone files, and the updates.
We've been automatically slaving all domains we host for years, whether or not the client actually uses our nameservers or not.
The only caveat I can think of would be if the slave nameserver doesn't have the same information as the "real" nameserver. You can avoid that problem by making your slave server authoritative only and not use it as a caching nameserver for general resolution.
Jeff
Why would it hurt if you end up slaving some domains and you never get a request for them?
Then your only resource "cost" would be the space it takes on your server for the zone files, and the updates.
We've been automatically slaving all domains we host for years, whether or not the client actually uses our nameservers or not.
The only caveat I can think of would be if the slave nameserver doesn't have the same information as the "real" nameserver. You can avoid that problem by making your slave server authoritative only and not use it as a caching nameserver for general resolution.
Jeff
- Joined
- Feb 27, 2003
- Messages
- 8,509
Hello,
Ok, so what do you think would be more flexible for this case?
A domain skip list, a domain allow list, a reseller skip/allow list? User Level?
I'm not looking to make it over complicated, simpler the better, but keeping in mind functionality for everyone.
John
Ok, so what do you think would be more flexible for this case?
A domain skip list, a domain allow list, a reseller skip/allow list? User Level?
I'm not looking to make it over complicated, simpler the better, but keeping in mind functionality for everyone.
John
icepick
Verified User
mmmm
It says user doesnt require another DA install, where are the scripts and instructions for the remote system?
I.e. I have a dedicated secondary DNS server and dont know how to get DA to talk to the backup DNS server.
Thanks
Barry
It says user doesnt require another DA install, where are the scripts and instructions for the remote system?
I.e. I have a dedicated secondary DNS server and dont know how to get DA to talk to the backup DNS server.
Thanks
Barry
Re: mmmm
I posted my ideas in http://www.directadmin.com/forum/showthread.php?s=&threadid=9790 on how you should be able to get it working. Note that it's just an idea and can be mistaken easilly.
Can't expect DirectAdmin to create scripts for a remote system without running DirectAdmin.
I think cPanel does it however with a free DNS only version, but I'm more than happy to pay that additional license fee for another server. It's worth it.
The next big thing I'm looking for would be Fallback MX. The same idea as DNS is now, so add servers to a pool and you're set. Hope to see that coming in the future.
icepick said:
I posted my ideas in http://www.directadmin.com/forum/showthread.php?s=&threadid=9790 on how you should be able to get it working. Note that it's just an idea and can be mistaken easilly.
Can't expect DirectAdmin to create scripts for a remote system without running DirectAdmin.
I think cPanel does it however with a free DNS only version, but I'm more than happy to pay that additional license fee for another server. It's worth it.
The next big thing I'm looking for would be Fallback MX. The same idea as DNS is now, so add servers to a pool and you're set. Hope to see that coming in the future.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Re: Re: mmmm
However you can also use our DNS master2slave system, which is well documented.
Jeff
I suppose spending the money might be a better option for many people.getUP said:
However you can also use our DNS master2slave system, which is well documented.
Jeff