change domain name with clustering loop

Version 1.264

Bugfix
Finished

If you have 2 DA servers, each pointing to each other with dns clustering (multiserver), when a domain name is changed at the User level, the remote server will call back to this server and delete the zone before the local one gets to rename it. This becaus the local server deletes and re-adds the zone on the remote machine, but fails to tell it that "this is with regards to clustering so *dont* call it to your own cluster". Fix will include a flag to mention to the remote box that it's with regards to clustering, thus the remote box won't call back to delete the zone. CMD_API_DNS_ADMIN

Interested to try DirectAdmin? Get a 30-day Free Trial!