Recent content by ingmarcofilippini

Actually from Plesk it seems to be connected correctly, but then it does not actually exchange zone data. If I launch this from the Plesk terminal: # rndc -b 192.168.1.101 -s 192.168.1.102 -p 953 -y rndc-key refresh example.com IN The result is this again: rndc: connection to remote host...

Hi @IgorG, thanks for your support. @tkalfaoglu Yes, I got confused; the "named" service has absolutely nothing to do with this problem. Thanks for your support. The problem actually I think is on the physical firewall of my network, ie from the outside the DNS slave server does not respond...

on /var/log/messages of the primary Plesk server I see these line a little suspicious: Nov 25 11:10:10 ccplesk01 named[5151]: unable to open '/etc/bind.keys'; using built-in keys instead The fact is that even if I uninstall the "Slave DNS Manager" extension and restart my Plesk server, the...

I confirm that the ports are open on the firewalls of the two servers and on the physical firewall (there is a NAT of all the ports on the public IP of the 2 machines). This is the output of nmap on the public IP of the slave server: PORT STATE SERVICE 53/tcp open domain 953/tcp open rndc...

I confirm that the keys are perfectly the same in both files. key "rndc-key-100.200.300.401" { algorithm hmac-md5; secret "NAQ2ZTBhMmi4MDBlNzliNjg0yTdjOA=="; }; on /var/log/messages of the secondary server I see these lines: Nov 25 09:56:40 slavedns named[12978]: network...

In my opinion the problem is on the primary Plesk machine, just because the status of "named" is on "failed", but maybe it has nothing to do with this, also because "named-chroot" on Plesk machine works correctly.

Thanks for the reply, Igor. I checked that too. Here a doubt arises: in the named.conf file I pasted my key provided by Plesk (the name of the key also has my public IP in the name), in the rndc.key file there was already a key. Do I just have to change "secret" or even the name of the key...

Hello to all, I have installed Plesk Obsidian 18.0.31 on a CentOS machine. Plesk works as the primary DNS for my websites and everything seems to work under the "named-chroot" service. I then installed the "Slave DNS Manager" extension following the official procedure and configuring the slave...