Bind or no Bind with dnsonly

webtipster

• October 12, 2019 11:22

Hi guys, So I created a new cpanel server and launched 2 vps dnsonly. Server uses 2 vps dnsonly as write only in cluster. 2 vps dnsonly use server as standalone in cluster. Everything seems to be working fine. Now my question is: on the server, do I leave "bind" dns or do I disable it? What are the pros/cons? What is the preferred setup? To me if enabled server bind keeps copies locally in the event vps dnsonly are lost/hacked etc... if disabled is frees the server from bind resource... Any thoughts are welcome! Thank you.

• 

  cPanelLauren

  • October 15, 2019 21:27

  If I were you I'd actually switch over to PowerDNS (we use it with a bind-backend) which we're moving to as default on cPanel/WHM as of V84 and use that on all servers. You should keep it active on the WebServer as well.

  0
• 

  webtipster

  • October 18, 2019 15:50

  Thanks you for your reply Lauren! Ah I see so switching to PowerDNS is preferred method moving forward v84+. So basically on the DNSonly servers switch from "bind" over to "powerdns" and on the WebServer switch to "powerdns" as well. Thank you again!

  If I were you I'd actually switch over to PowerDNS (we use it with a bind-backend) which we're moving to as default on cPanel/WHM as of V84 and use that on all servers. You should keep it active on the WebServer as well.

  
  

  0

Please sign in to leave a comment.