plesk / ext-slave-dns-manager

The extension for managing a remote slave DNS server via rndc protocol (bind).
Other
16 stars 12 forks source link

Slave server does not allowed to transfer zone #5

Open sugdyzhekov opened 8 years ago

sugdyzhekov commented 8 years ago

Impact Slave server could not fetch domain zone RRs from master

STR

  1. Install extension
  2. Register slave server
  3. Create domain
  4. Check slave server

Expected result Slave server fetched domain zone RRs from master

Actual result Slave server could not fetch domain zone RRs from master

Additional info

ilyakruchinin commented 7 years ago

I'm facing the same issue. This file is responsible for adding the server's IP to the DNS Template using Plesk API, but it doesn't seem to do the job (on Windows only - Linux is fine). https://github.com/plesk/ext-slave-dns-manager/blob/master/plib/library/Acl.php

ayamshanov commented 7 years ago

This XML API does not support in Plesk for Windows - https://docs.plesk.com/en-US/onyx/api-rpc/reference/managing-dns/managing-acl/adding-hosts-to-acl.34906/ ("This operation is available on Linux only")

wice222 commented 6 years ago

Same issue here, Plesk shows that connection is established, but , green light is shining... but Slave bind is not getting any records from master DNS on PLESK ...

ayamshanov commented 6 years ago

Usually, it happens because of misconfiguration firewall rules or BIND on slave DNS.

Could you provide more technical details? What version of Plesk do you use? What OS do you use as slave DNS? Did you see messages about DNS in /var/log/messages while zone syncing?

Did you see https://talk.plesk.com/articles/how-to-start-with-slave-dns-manager.12/?

wice222 commented 6 years ago

I have fully disabled Firewall, and selinux, ... to make sure it has nothing to do with security issues using PLESK, Latest, OS CentOS 7, as slave

>named -V
BIND 9.9.4-RedHat-9.9.4-50.el7_3.1

Did you see messages about DNS in /var/log/messages

On which server, ? I can see some strange error messages on slave DNS, something like unresolved host trough IPv6.... not sure if that is related to sinhronisation sins I configured all to be working via IPv4 ...