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

Issue Using Plesk with the AWS Route 53 extension.

husentiel91

New Pleskian
Hi, anyone got any experience of using Route 53 alongside Plesk?
I'm trying to get my head around how its meant to be set up. If I'm pointing the domain at my AWS name servers, should I have DNS for that domain in plesk set to Master or Slave?
192.168.0.1 routerlogin 192.168.l.l
 
Last edited:
You don't need to override anything specifically. You just specify the Amazon nameserver for your domain at the registrar side. That's all.
Thus, you edit the DNS zone in Plesk, and these changes are synchronized in the Amazon nameserver, which, in turn, uses the registrar for your domain.
 
Just a question, the extension works with ALL domains in a server or only with the domains you want in a server?

Thank you
 
Just a question, the extension works with ALL domains in a server or only with the domains you want in a server?

Thank you
Zones of all your domains will be synchronized with the Amazon Route 53.
More details can be found here:

 
Back
Top