• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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