• 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.

Secondary DNS can't transfer zone info - firewall issue?

matthew@

New Pleskian
Just setting up domains on Plesk (FreeBSD) and trying to get a secondary DNS server working, without much luck - can anyone help?

I think it's a firewall issue. Assume: ns.domain1.com is the primary DNS on this server, using IP 1.1.1.2. I'm setting up domain2.com on there on IP 1.1.1.1 and trying to use a secondary DNS for it, using secondary DNS server ns.second.com, 2.2.2.2. I have:

* In Server > DNS > Common ACL, added 2.2.2.2

* In Domains > domain2.com > DNS, added NS records:
domain2.com > NS > ns.domain1.com
domain2.com > NS > ns.second.com

* In Modules > Firewall, added:
Allow outgoing to 2.2.2.2 on 53tcp, 53udp
(The built-in DNS rule allows incoming from all to 53?)

* In /etc/named.conf, uncommented:
query-source address * port 53 (although I'm not sure this was necessary)

I'm pretty sure that my ns.domain1.com is all working fine, 'cos domain2.com is up and running. However, when I try to add it to the secondary DNS service:

* Master DNS: 1.1.1.2
* Domain name: domain2.com

It gives me an error: 'ns.second.com can't read from primary server. hint: check firewall.'

Am I missing something? (Likely) Any insights much appreciated.
 
Check out ARTs secondary dns feature, it works great and may have some firewall configuration information in the setup as well.
 
Check out ARTs secondary dns feature, it works great and may have some firewall configuration information in the setup as well.

Hi, thanks for the tip - I'm looking into this, it looks useful. Meantime my problem seems to have resolved itself of its own accord. Don't know why but I'm not complaining!
 
Back
Top