Facebook
Twitter
Matt N
New Pleskian
Hi All,
I am hoping that someone can provide some pointers on using the AWS Route 53 extension with Plesk and AWS to deliver WhiteLabel DNS servers using AWS for my hosted domains.
I am running Plesk Obsidian 18.0.20 (although the same behaviour exists in Onyx 17.8.11 as well).
Following the details in this article. I have set up the AWS extension, and data is pushing into AWS all okay.
In Plesk:
in my own domain (example.com) I have set up the following records:
For my clients domains, the DNS records listed are :
This has been working well for some time. Now, I want to use AWS Route 53.
I have created a reusable Delegation Set - and got 4 DNS servers and their associated IPv4 addresses.
When I remove, then sync all domains from plesk all the zones are created in Route53 - however, all zones have different NS records to the actual Re-usable delegation set that was created. Even my own domain (example.com) doesn't have the reusable delegation set that is listed.
I don't want to have to go and change the NS records in AWS for each of my client's zones - that kinda defeats the purpose of the integration.
I can get my head around having to initially configure my own white-label/vanity name server records in my AWS zone - ie changing :
to
but my confusion - is that the default AWS NS records that exist in my NS record in my zone at AWS:
I am hoping that someone can provide some pointers on using the AWS Route 53 extension with Plesk and AWS to deliver WhiteLabel DNS servers using AWS for my hosted domains.
I am running Plesk Obsidian 18.0.20 (although the same behaviour exists in Onyx 17.8.11 as well).
Following the details in this article. I have set up the AWS extension, and data is pushing into AWS all okay.
In Plesk:
in my own domain (example.com) I have set up the following records:
Code:
ns1.example.com A 100.10.20.40
ns2.example.com A 100.20.40.50
ns3.example.com A 100.30.30.60
ns4.example.com A 100.40.30.80
example.com. NS ns1.example.com
example.com. NS ns2.example.com
example.com. NS ns3.example.com
example.com. NS ns4.example.comFor my clients domains, the DNS records listed are :
Code:
clientdomain.com. NS ns1.example.com
clientdomain.com. NS ns2.example.com
clientdomain.com. NS ns3.example.com
clientdomain.com. NS ns4.example.comThis has been working well for some time. Now, I want to use AWS Route 53.
I have created a reusable Delegation Set - and got 4 DNS servers and their associated IPv4 addresses.
When I remove, then sync all domains from plesk all the zones are created in Route53 - however, all zones have different NS records to the actual Re-usable delegation set that was created. Even my own domain (example.com) doesn't have the reusable delegation set that is listed.
I don't want to have to go and change the NS records in AWS for each of my client's zones - that kinda defeats the purpose of the integration.
I can get my head around having to initially configure my own white-label/vanity name server records in my AWS zone - ie changing :
Code:
ns-1984.awsdns-56.co.uk.
ns-862.awsdns-43.net.
ns-1398.awsdns-46.org.
ns-277.awsdns-34.com.to
Code:
ns1.example.com.
ns2.example.com.
ns3.example.com.
ns4.example.com.but my confusion - is that the default AWS NS records that exist in my NS record in my zone at AWS:
- don't match the Reusable Delegation Set that Plesk shows
- don't appear in each of my client's zones
