[RESOLVED][S.O.S] bind server not syncing

1

Hello!

Last updated hestiacp (v1.4.17) master and slave is.
Debian 9 64Bit, api allowed, api_allowed_ip: allow-all

Not syncing master to slave dns server error:

Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: client 87.229.71.37#37217 (server1huns2.pgaming.hu.pgaming.hu): query (cache) ‘server1huns2.pgaming.hu.pgaming.hu/AAAA/IN’ denied
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: REFUSED unexpected RCODE resolving ‘server1huns2.pgaming.hu.pgaming.hu/A/IN’: 87.229.71.37#53
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: REFUSED unexpected RCODE resolving ‘server1huns2.pgaming.hu.pgaming.hu/AAAA/IN’: 87.229.71.37#53
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: client 87.229.71.37#59715 (server1huns2.pgaming.hu): query (cache) ‘server1huns2.pgaming.hu/MX/IN’ denied
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: REFUSED unexpected RCODE resolving ‘server1huns2.pgaming.hu/MX/IN’: 87.229.71.37#53
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: client 45.67.156.199#53152 (server1huns2.pgaming.hu): query (cache) ‘server1huns2.pgaming.hu/MX/IN’ denied
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: REFUSED unexpected RCODE resolving ‘server1huns2.pgaming.hu/MX/IN’: 45.67.156.199#53
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: client 87.229.71.37#43792 (server1huns2.pgaming.hu): query (cache) ‘server1huns2.pgaming.hu/MX/IN’ denied
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: REFUSED unexpected RCODE resolving ‘server1huns2.pgaming.hu/MX/IN’: 87.229.71.37#53
Oct 31 23:33:24 server1huns2.pgaming.hu named[29083]: client 45.67.156.199#39856 (server1huns2.pgaming.hu): query (cache) ‘server1huns2.pgaming.hu/MX/IN’ denied

It still worked with the previous update. Last on October 22nd.

2

We haven’t released any update since 29 of September…

How are you syncing the DNS records between master and slave?

3

https://docs.hestiacp.com/admin_docs/dns.html

I went through this for the first time. Then you sync yourself with the following command:

sudo /usr/local/hestia/bin/v-sync-dns-cluster

Sorry, now I look, my email has not been synced since September 14th, at least it still sent quite a few emails.

4

Check if you can connect with the api.

Also make sure ip of your main server is in the allowed ip list or allow-all

https://docs.hestiacp.com/admin_docs/api.html#unable-to-connect-to-the-api

5

In what log should the error be searched? nowhere is nothing!

6

Download this file and upload it as api.php

https://gist.githubusercontent.com/jaapmarcus/86c0e588a8ba69a6f521e3ea370708a4/raw/e164f5226eb909b0babc30e77029ba3862b91c56/gistfile1.txt

And then try connecting to your slave it should.

7

https://192.168.80.254:8083/api/
string(545) "HTTP/1.1 200 OK
Server: nginx
Date: Mon, 01 Nov 2021 06:47:45 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

USER PKG WEB DNS MAIL DB DISK BW SPND DATE

admin default 1 1 0 0 4 0 no 2021-10-31
dns-cluster default 0 0 0 0 1 0 no 2021-10-31

192.168.80.254 (internal ip)

There was a vestacp in front of him, he stopped only once. a couple of pages had already shut down yesterday, so I deleted it and installed hestiacp on it as well.

8

VestaCP received an update is quite broken at the moment…

9

I changed it to Hestiacp last night. (Removed full data Vesta and install Hestiacp)

Resolved:

Delete dns-cluster account, and test:

Error: dns-cluster doesn’t exist

and recreate dns-cluster account and working! :slight_smile: :slight_smile: