• 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 How to use amazon route 53 as dns

agaitan

Basic Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
18.0.49
Hi i currently use route 53 of amazon for this use case:

1. i got my domain mydomain.org registered in amazon, i have created 2 nameserver like ns1.mydomain.org and ns2.mydomain.org and set my two plesk ips
2. when i create new domains , new domains should have the ns: ns1.mydomain.org and ns2.mydomain.org, that works perfect

now i would like to implement route 53 using the plesk addon, what should i do to maintain my ns1 and ns2 mydomain.org nameservers? or that will change?

thank you
 
Keep in mind that Route 53 can be used as a DNS provider, as well as a domain register. Those are two separate things. It's seems like you're currently only using Route 53 to register domains and use your Plesk server to run your DNS.

The Plesk Route 53 extension however can only be used to run the Route 53 DNS. The extension synchronizes the DNS zones on your Plesk server to Route 53. In order to use the Route 53 DNS you'll need to change the name servers of your domains to the name servers of Route 53.

You can still register your domains with Route 53 of course. But that not what the Plesk Route 53 extension is used for.

Hope this explanation makes sense.
 
Keep in mind that Route 53 can be used as a DNS provider, as well as a domain register. Those are two separate things. It's seems like you're currently only using Route 53 to register domains and use your Plesk server to run your DNS.

The Plesk Route 53 extension however can only be used to run the Route 53 DNS. The extension synchronizes the DNS zones on your Plesk server to Route 53. In order to use the Route 53 DNS you'll need to change the name servers of your domains to the name servers of Route 53.

You can still register your domains with Route 53 of course. But that not what the Plesk Route 53 extension is used for.

Hope this explanation makes sense.
But what about using ns1.mydomain.org ns2 white labeled, or you guys recommend me to use the Amazon default Ns?
 
But what about using ns1.mydomain.org ns2 white labeled, or you guys recommend me to use the Amazon default Ns?
See: https://support.plesk.com/hc/en-us/...White-Label-DNS-with-Amazon-Route-53-in-Plesk

EDIT: this is a more indepth article about using white label with Route 53:

Also by using Amazon route 53 my Dns propagations should be faster correct?
I don't see why that would make a difference. But it could be true. I am not sure.
 
Back
Top