Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Help with pfSense, cPanel DNS Only and Plesk Slave DNS Manager

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 490 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      easy-hostingnz
      last edited by

      To me this is not a Plesk/Slave DNS Manager issue, but hoping someone has tried the same setup.

      pfSense - Plesk
      - Almalinux 8.7 with cPanel DNS Only
      - cPanel

      Azure - cPanel DNS Only

      • Setup behind pfSense is 1:1 NAT.
      • Plesk and cPanel are in same external range. Almalinux box on different range. All on same internal range.
      • cPanel and Plesk can talk to Azure box, but can't talk to Almalinux box.
      • cPanel DNS Cluster configuration check reports back the information from the Almalinux box (The Trust Relationship has been established. The remote server, x.x.x.x is running WHM version: 10.0.0. The new role for x.x.x.x is write-only.).
      • Firewall disabled on Almalinux.
      • pfSense firewall rules are in place for necessary ports.
      • Port scans (multiple sites) show the ports are open.
      • cPanel shows the error: "Could not communicate with remote API server.".
      • Plesk shows the error: "rndc: recv failed: connection reset.".
      • SELinux has been disabled.

      Nothing is coming up in pfSense saying that traffic is blocked between Plesk/cPanel and the Almalinux box. Telnet to the ports go through.

      The only other thing I can think of is reading somewhere that they can't be on the same internal IP range if you're doing NAT of any sort.

      Any help with sorting this would be greatly appreciated!

      E 1 Reply Last reply Reply Quote 0
      • E
        easy-hostingnz @easy-hostingnz
        last edited by

        OK, just setup the DNS Clustering on the Azure box to the Almalinux box and that worked. So it's either a failure of the API key or the internal IP range issue.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.