You can’t have more than one set of zones authoritative in DNS. Either route 53 will be your name servers for your zone or light sail will.
Just create the dns record for Wordpress and the alb etc in route53. That is a supported setup.
Your R53 DNS record can be an alias type and that will point to your Application load balancer in Lightsail. Here is the source: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/add-alias-record-for-lightsail-load-balancer
If you have your Route53 Public zone created for your registered domain, then that is enough for you to create a record and point that record to resolve to your Lightsail instance IP. Follow this: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-route-53-to-point-a-domain-to-an-instance
I had an issue when I moved a DNS zone from LightSail to Route53. Possibly the resolution will help your situation. Scenario: Moving a domain from another registrar to Route53. A LightSail DNS zone already existed pointing to a LightSail instance. My original DNS records already updated to use the LightSail NS records and with A pointing to the LightSail instance IP. This setup was working. Actions:
- : Transfer the domain to AWS via Route53 wizard. Success.
- : Lower TTL for NS and other records in the LightSail zone.
- : Setup Route53 Hosted Zone. Imported Lightsail zone records using the very helpful script here.
- : After TTL expired, delete LightSail Zone.
Result: Route53 set up with Hosted Zone correctly. But 3 days later, still the domain was not resolving.
Tried using the LightSail NS records in the Route53 Zone - bad idea, didn't work, unglued things further.
Deleted and re-created the Route53 Hosted Zone - did not help
Every doc/post I could find on the subject didn't help either.
In the LightSail dashboard, I noticed a new entry for the Registered Domain (see images), with a warning about there being no LS DNS Zone for it and two options to manage the registration in either LightSail or Route53. I chose LightSail expecting it to not work because there is no DNS zone for the domain in LightSail and I'd already spent time checking it in Route53.. It did work and showed the four original LightSail NS records, which were editable.
I changed them to the Route53 NS records and bingo! dig started showing answers. Fixed.
- The Registration of the domain through Route53 automatically created a record of the registration in LightSail.
- It did not create a LightSail DNS Zone because it already existed.
- When I deleted the DNS Zone in LightSail, I thought I had deleted the zone - but apparently not! There is some NS information in the Registered Domain record which is 'in the resolution chain'. It isn't documented as far as I can tell.
- It was an action in Route53 that created the Registered Domain record in LightSail - why did it use LightSail NS records?
- It should be documented that this record is somehow over-riding the Route53 NS records.
The Registered Domain records.
Two choices for management.
The NS records in a place that isn't a zone but is acting like one !
I hope this helps someone, John
- asked 3 months ago
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- EXPERTpublished 4 days ago
- EXPERTpublished 12 days ago