Knowledge Base

Putting Your Website Online – Using a Third-Party DNS Service Synced with Plesk

A number of DNS services can integrate with Plesk, for example, DigitalOcean DNS, Amazon Route 53, Azure DNS, and so on.
You can use them to put your website online, which has the following advantages:

The DNS records are stored in the DNS service but you can manage them directly in Plesk.
DNS zones will be automatically synced between Plesk and the DNS service.
No need to set up and maintain a slave DNS server.
The DNS services mentioned above offer DNS hosting with three or more different name servers.
This will reduce your Plesk server load and improve DNS hosting reliability.

Amazon Route 53

Watch the video tutorial

Amazon Route 53 is a paid DNS service, which offers four name servers.

You can set up DNS hosting before or after adding domains to Plesk.
Either way, both new and existing domains will be automatically synced with the DNS service.

To put your website online with Amazon Route 53:

Log in to your Amazon root user or IAM user account.
Save the access key ID and the secret access key of your account.
If you use the IAM user account, make sure to grant the route53:* and route53domains:* permissions to the account.
Log in to Plesk.
Make sure that the DigitalOcean DNS, Slave DNS Manager, and Microsoft Azure DNS extensions are not installed.
If they are, remove them to avoid conflict with Amazon Route 53.
Go to Extensions, look for the Amazon Route 53 extension, and then click Get it free to install it.
Next to the installed extension, click Open.
Select the key type that you use: root account or IAM user account.
Paste the access key ID and the secret access key that you got during step 2.
Select the “Manage NS and SOA records” and the “Turn on Amazon Web Service Route 53” checkboxes and then click Log in.
Go to your registrar’s dashboard and change the registrar’s nameservers to those of Amazon Route 53.
Find out your Amazon Route 53 name servers.