: Trying to understand white label nameserver aws route53 I'm having a problem understanding how "white label" nameservers might work, at Amazon Route53. Here is what I have: Domain destination.com
I'm having a problem understanding how "white label" nameservers might work, at Amazon Route53. Here is what I have:
Domain destination.com is hosted at hosty.com and registrar has ns1.hosty.com and ns2.hosty.com as nameservers.
Using alias A record at aws route53 to handle mysite.com -> mysite.com, mysite.com has a CNAME pointer to destination.com. Registrar has the normal Amazon ns-xxx-aws-xx.com and ns-xxx-aws-xx.net as nameservers.
At this point, everything works correctly and any requests for mysite.com or mysite.com will route to destination.com (WordPress mulitsite subdomains). Works great - site comes up as expected.
Now I want to implement white-label nameservers at route53. I followed the directions I found in the documentation, and believe I've set up a set of nameservers using a new domain name I registered. When I ping these, they resolve to the original route53 IP addresses for the Amazon nameservers, so I think they are correct.
ns1.mypath.net
ns2.mypath.net
ns3.mypath.net
ns4.mypath.net
I want to be able to go to the registrar for mysite.com, set the new mypath.net nameservers there -- and have requests to mysite.com route to the hosted zone for mysite.com at aws, so it ends up redirecting to destination.com (as it was with the normal aws nameservers specified).
I just can't figure out how to wire this.
More posts by @Kaufman445
1 Comments
Sorted by latest first Latest Oldest Best
After some sleep, I got it working.
I was missing one step. I had already established a hosted zone for mysite.com, within route 53. When that was set up it was handed a set of nameservers from aws. I simply edited those and replaced with:
ns1.mypath.net
ns2.mypath.net
ns3.mypath.net
ns4.mypath.net
That was wrong, since the original nameservers are now "disconnected" from the nameservers that mypath.net is wrapping.
So, I deleted the hosted zone for mysite.com and I recreated it from the aws CLI:
aws route53 create-hosted-zone --caller-reference my-nameservers --name mysite.com --delegation-set-id /delegationset/XXXXXXXXXXXXXX
This assures that the domain mysite.com is tied to that same nameserver delegation set I created for mypath.net
Then, updated the NS records for mysite.com to use the white-label nameservers, re-did my Alias record pointing to the statically mapped s3 bucket (to handle the mapping to www) -- and it seems to work fine now.
Whew.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.