• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Plesk SLAVEDNS Troubleshooting Problem

Consertis

New Pleskian
I am currently having problems getting my slave dns servers up and running.

First of all: Both servers are connected via BIND9 and are shown as green and working properly in the Plesk Dashboard.

But now I have the problem that somehow still no sync takes place. The SLAVE servers can not resolve the address:

; <<>> DiG 9.16.1-Ubuntu <<>> A sipvox.nex @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3622
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 2a632a1079420611010000625964cd96d1492d2742b8bd (good)
;; QUESTION SECTION:
;sipvox.nex. IN A

;; query time: 3927 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Apr 15 12:27:57 UTC 2022
;; MSG SIZE rcvd: 67


However, it works fine on the Plesk server itself:

; <<>> DiG 9.16.1-Ubuntu <<>> A sipvox.net @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26618
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: ; udp: 4096
; COOKIE: 35a2b43eab2e911d010000625966009f0a806e707f2a3c (good)
;; QUESTION SECTION:
;sipvox.net. IN A

;; ANSWER SECTION:
sipvox.net. 86400 IN A 212.232.26.248

;; query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Apr 15 12:33:04 UTC 2022
;; MSG SIZE rcvd: 83

I don't know what to do anymore.

In the firewall all ports are opened correctly (port: 53 for DNS).

I think somehow the transfer of the adresses dont work properly, but i cant say if im right or not.
I am grateful for any help !
 
Apr 15 12:51:36 tu2040 named[43203]: validating ./NS: no valid signature found
Apr 15 12:51:36 tu2040 named[43203]: no valid RRSIG resolving './NS/IN': 192.33.4.12#53
Apr 15 12:51:36 tu2040 named[43203]: validating ./NS: no valid signature found
Apr 15 12:51:36 tu2040 named[43203]: no valid RRSIG resolving './NS/IN': 199.7.83.42#53
Apr 15 12:51:36 tu2040 named[43203]: validating ./NS: no valid signature found
Apr 15 12:51:36 tu2040 named[43203]: no valid RRSIG resolving './NS/IN': 192.5.5.241#53
Apr 15 12:51:36 tu2040 named[43203]: resolver priming query complete
Apr 15 12:51:40 tu2040 named[43203]: validating net/DS: no valid signature found
Apr 15 12:51:40 tu2040 named[43203]: broken trust chain resolving 'sipvox.net/A/IN': 212.232.26.248#53
Apr 15 12:52:05 tu2040 named[43203]: managed-keys-zone: DNSKEY set for zone '.' could not be verified with current keys

Bind shows this as Error Message when typing in the command: sudo service bind9 status
 
Back
Top