After updating the zone file
Once ready, run the script with all the arguments in place.Then create /etc/bind/repos/$and put inside: Where ‘domain.com’ is the first domain you are managing with gitzone.
When you add your domain to Office 365, typically your domain's MX record is updated (by you or Office 365) to point to Office 365, and ALL email sent to that domain will start coming to Office 365.The git url will be composed of the hostname of the machine where is has been installed and the username chosen: The command above will clone the new gitzone repository into a directory gitzone-admin.If you aren’t familiar with git, this is a good time to go study it.If there’s an error in a file being pushed then the push is rejected, thus only correct files are stored on the server. Gitzone-shell is similar to git-shell but it restricts the user to the zones repository and provides some additional commands for dynamic DNS updates & SSH key management.Gitzone-shell and the Gitzone-install scripts are written in Zsh shell script.Make sure you've created mailboxes in Office 365 for everyone who has email on your domain BEFORE you change the MX record.
What if you don't want to move email for everyone on your domain to Office 365?
% git commit -m 'commit msg' % git push origin && git pull In order to do automatic dynamic DNS updates, create an SSH key without a password and use the add-key command to add it with a command= parameter which has an update-record command in it, see the example in the previous section.
This way the host doing the updates does not have access to the git repository as it is restricted to the specified command only.
First install Bind9 (not covered by this documentation).
Then install all scripts in the prefix /bin path and /libexec This script assumes that a user with ‘username’ (first argument) already exists: anyone with access to this user will be in control of gitzone, since access is managed via ssh authentication.
We can help you track down issues with your domain's DNS setup.