DNS Clusters are broken in V16
-
anthonyrossbach
- Posts: 21
- Joined: Thu May 21, 2015 6:00 am
DNS Clusters are broken in V16
The problems with V16 have caused 2 servers to need to be scraped, 3 others to need massive code changes and me manually updating the backend of VestaCP to make it work again, now here are 2 more servers in need of fixes that are not working at all. I have integrated everything into the CP API and now the problems are driving me crazy, the one for today?
DNS will not sync, and gives no errors that I can see.
I am wondering if anyone has found a reason for the clusters to not sync and if there is a fix, or a forceful way to sync that I can use instead, this causing huge problems and downtime.
DNS will not sync, and gives no errors that I can see.
I am wondering if anyone has found a reason for the clusters to not sync and if there is a fix, or a forceful way to sync that I can use instead, this causing huge problems and downtime.
Re: DNS Clusters are broken in V16
Mine are working?anthonyrossbach wrote:The problems with V16 have caused 2 servers to need to be scraped, 3 others to need massive code changes and me manually updating the backend of VestaCP to make it work again, now here are 2 more servers in need of fixes that are not working at all. I have integrated everything into the CP API and now the problems are driving me crazy, the one for today?
DNS will not sync, and gives no errors that I can see.
I am wondering if anyone has found a reason for the clusters to not sync and if there is a fix, or a forceful way to sync that I can use instead, this causing huge problems and downtime.
This code executed will forcefully update clusters so if you execute it on server 1 - server 1 updates the cluster it's connected to. (this is run every 5 minutes in a Vesta cronjob)
Code: Select all
v-sync-dns-cluster