Rebuilding cluster v-delete-remote-dns-host

Community Support DNS
1

Hello! I’m trying to move from a Master → Slave setup to a Master → Master DNS cluster.

When I try to run in the server 2, v-delete-remote-dns-host, the command just hangs and doesn’t respond. On the other server, it works without any issues.

After checking /var/log/hestia/error.log, I see multiple errors associated with v-delete-remote-dns-record:

v-delete-remote-dns-record  'dns-cluster' 'domain.tld' '18' [Error 15]
v-delete-remote-dns-record  'dns-cluster' 'domain.tld' '18' [Error 15]
v-delete-remote-dns-record  'dns-cluster' 'domain.tld' '19' [Error 15]
v-delete-remote-dns-record  'dns-cluster' 'domain.tld' '19' [Error 15]
v-delete-remote-dns-domain  'dns-cluster' 'domain.tld' [Error 15]
v-delete-remote-dns-domain  'dns-cluster' 'domain.tld' [Error 15]
v-delete-remote-dns-domain  'dns-cluster' 'domain.tld' [Error 15]
v-delete-remote-dns-domain  'dns-cluster' 'domain.tld' [Error 15]

Is there a way to manually delete the remote DNS server to rebuild the DNS cluster?

2

I had a moment of clarity while writing this; I found the file at

/usr/local/hestia/conf/dns-cluster.conf

Im rebuilding my cluster :slight_smile:

1 Like
3

v-list-remote-dns-hosts
v-delete-remote-dns-host hostname.domain.com
Then just re-add it.

You can add remote dns by API method and if you need to sync the dns for some reason you can use this

v-sync-dns-cluster hostname.domain.com

Make sure both servers are whitelisted to each other.

1 Like
4

Hi guys, hope someone can help me, I had a weird issue with this.

1 scenario: I have installed 2 virtual machines with ubuntu 22.04 and Hestia 1.9.3 I made a DNS cluster master<–>master using API Keys all good with testing looks like, the dns zones creaded on server 1 where added to server 2.

2 scenario: I recently installed 2 servers with Ubuntu 22.04 and Hestia 1.9.2 , both updated to Hestia 1.9.3, due to some errors with 1.9.2 I was able to set cluster using Legacy API, I wanted to change them to API Keys (as I used to have it time ago with version 1.8.12).

I was using following commands:
v-list-remote-dns-hosts —> all ok here

v-delete-remote-dns-host —> This doesn’t work, error said there was no server with that subdomain

So, I manually erase remote dns host from dns-cluster.conf on both servers, then I created API Keys under my custom admin user, later I run command to add remote dns server (they were already whitelisted on each server on API security settings), after this, few minutes later dns zones were replicated on sencond server, but just few later they were erased from server 2 and never updated again even running manually the command created on cron jobs.

UPDATE: just to update on this if someone is under same situation, first at all: Thanks God for VPS snapshots hahahaa.

So at the end, before doing anything I tried before, snapshots were taken, I rolledback everything I have an little issue with DNS zones so just restore last backup just for DNS, once working again as normal confirmed my cluster was working as previously new snapshots were taken, next I have manually deleted host on dns-cluster.conf, have delete my dns user, later I have created dns users again, API Keys on my custom admin user, and run v-add-remote-dns-host script, all is working now.