• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Best dns practices

ufo56

New Pleskian
Hello

Whats the most "foolproof" method for dns for websites on Plesk?

Do you give your client(s) your hosting domain DNS, example : dns1.yourhosting.com dns2.yourhosting.com or they use dns1.clientdomain.com dns2.clientdomain.com in registrar settings (default plesk template settings)?

I have tried past week many solutions and can't figure out whats the best. To be honest im confused already...


What about when you want migrate client to other server, how to manage like that he does not have to change domain ns in registrar?

Route53? Azure? Slave dns?
 
Last edited:
Use Cloudflare DNS -- not for CDN, but for DNS. Using for years, totally free, easy to setup, and we've experienced no DNS downtime ever. Resolves in 1-2 ms anywhere in the world and instant if user is using 1.1.1.1 as their resolver. 1-click to redirect from one server to another and/or alter records.

A great 'set it and forget it' without worrying about your DNS. SPF, DKIM and CAA easy as well. Forget the old idea of vanity name servers...
 
Back
Top