If you are looking for the options to avoid any DNS-related downtime or the way to manage dns across all server you have, you might consider to set up dns cluster.
- Create user dns-cluster on a server which will be used as dns slave
- Run following command on a master:
v-add-remote-dns-host ns2.yourhost.com 8083 admin pa$$sw0rd
Password and host name should be replaced with relevant data
This way you can set up master->slave or master-master-master cluster. There is no limitation on how to chain dns servers.
I also want to talk about some problems that may arise in this bunch
Q: There are two servers in the dns cluster. With one, problems started, a new one was raised. The bottom line is how to remove the slave server from the dns cluster. So that the synchronization does not go to him anymore?
A: On dns-master host type in shell:
v-delete-remote-dns-host slave.dns-host.com
Q:There are two servers xxx and yyy
When creating a bunch from xxx to yyy, an api error occurs:
Error: api connection to 111.111.111.111 failed
When creating a bunch from xxx to yyy, an api error occurs:
Error: api connection to 111.111.111.111 failed
A: Perhaps the wrong user password admin
Q: How to see the list of slave dns-servers ?
A: v-list-remote-dns-hosts
Similar Posts:
- How to migrate user to the new server VestaCP
- how to fix login error NO LANGUAGE DEFINED on VestaCP
- How to add remote MySQL database server VestaCP
- Config and log locations on a Debian and Ubuntu on VestaCP
- Description of web templates for Vesta control panel
1,829