- 최신
- 최다 투표
- 가장 많은 댓글
I followed this procedure as well. I have a hosted zone on my AWS that is just to use an API gateway for a parent domain hosted on godaddy. I have taken the 4 NS servers and put them in as records with the full subdomain name on the godaddy dns config. However, I am still not getting the traffic routed correctly to my AWS hosted zone. Do I need to add a subdomain and forward it to something in the Godaddy DNS management or just add the 4 NS entries?
I know my AWS side is correct because if I route the enter parent domain by replacing the Nameservers with these 4, it works, bur I lose the ability to route to my parent domain (all non sub).
Thanks.
Hi,
Thank you for reaching out to us! I understand you want to host subdomains on R53 and your parent domain is hosted on GoDaddy.
The procedure you are following is right, expect that you are creating CNAME at go daddy for your subdomain.
To have subdomain delegated to R53, you would need to create a NS record at GoDaddy with the name servers given by R53 hosted zone and not CNAME.
For ex)
Record Type = NS
Name = beta1.domainname.com
Value = ns-???.awsdns-??.com
TTL = 1/2 Hour
Please look at https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingNewSubdomain.html#UpdateDNSParentDomain for further information.
Have a nice day! :)
And if any of you ever provided the actual domain names you're using other forum members could look at the setup, as seen in the public information on the internet, and possibly give you pointers.
Did you put the whole fdqn in the godaddy NS record or just the subdomain name?
Example from above should be like this.
Record Type = NS Name = beta1 Value = ns-???.awsdns-??.com TTL = 1/2 Hour
If you did this in Godaddy Record Type = NS Name = beta1.domainname.com Value = ns-???.awsdns-??.com TTL = 1/2 Hour
The subdomain you are technically delegating name service for is "beta1.domainname.com.domainname.com"