I wanted to know if such a scenario is possible:
I have a domain hosted in GoDaddy - say example.com
I go to Cloudflare, create that domain, take the nameservers, and configure them in GoDaddy
I go to AWS Route53, create hosted zone, take 4x NS records that were generated and insert them in Cloudflare as NS records separately
So its: GoDaddy -> Cloudflare -> AWS Route53
And now - should I be able to manage my domains via AWS Route53?
I figured it out and it seems that doing what I described above is impossible for the root domain, like example.com.
Meaning that if in my domain registrar I point to different Nameservers for example.com only those are valid and I cannot configure NS records for example.com further. So:
I buy example.com at GoDaddy -> all good
I login to Cloudflare, add new domain, receive Nameservers: a.ns.cloudflare.com and b.ns.cloudflare.com -> all good
I go to GoDaddy and configure Nameservers to be those from point 2 -> all good
Now I login to AWS, go to AWS Route53 and generate HostedZone for example.com. I receive 4 Nameservers: a.aws.com, ... d.aws.com -> all good
Now I go to Cloudflare example.com domain records and try to configure the 4x NS records for those four I got from Route53 -> thats NOT good
In point 5 this is not going to work.
However!
It is possible with subdomains. So if in point 4. I would have created HostedZone for test.example.com I would have been able to go to Cloudflare and point test.example.com with NS records to those 4x Nameservers that I get from Route53 and manage test.example.com and *.test.example.com from Route53.
If I am wrong in anything please correct me!
Related
I'm in the process of migrating a bunch of stuff over to AWS and I've hit a bit of a snag in relation to Route53, specifically with vanity nameservers.
Current setup (not on Route53);
ns1.example.com - Glue records pointing to IP address of current DNS provider
ns2.example.com - Glue records pointing to IP address of current DNS provider
Various domains, all set to ns1.example.com for their authorities nameservers at the registrar;
website-one.com
website-two.com
etc.
So I've been doing some testing with getting this migrated to Route53, and I'm not sure this is straight forward to do when you want to use a single vanity nameserver across multiple domains. When I create 2x hosted zones in Route53, they get different nameservers that Route53 automatically generates, i.e.;
example.com Hosted Zone - ns-123.awsdns-456.com
website-one.com Hosted Zone - ns-789.awsdns-321.com
website-two.com Hosted Zone - ns-987.awsdns-654.com
etc.
As such, with there only being one option at the registrar for example.com to configure the Glue Records;
ns1.example.com - pointing to IP Address of the Route53 nameserver, i.e. ns-123.awsdns-456.com (1.2.3.4)
ns2.example.com - pointing to IP Address of the Route53 nameserver, i.e. ns-123.awsdns-456.net (1.2.3.4)
Then I'm a bit lost as to how you're supposed to get this kind of setup working in Route53.
The reason for wanting this is to avoid having to go messing around with the nameservers at all of the different domains, some of which I can easily access, others are a bit of a pain to get access to so they can be updated.
Thoughts on how to best approach this?
Suppose I own example.com.
I delegate the subdomain www.example.com to a particular set of NS that is say a Route53 Hosted Zone. The rest of the example.com zone is not on R53 and contains important information for other subdomain/records. You can consider this Zone 1, and you can consider the new R53 Hosted Zone as Zone 2.
I want to have www.example.com CNAMEd to a particular endpoint, say a cloudfront distribution.
Since I can't CNAME the apex domain, instead hosted zone 2 is created in R53 with the original apex domain: example.com.
Then, inside that hosted zone, there is a record for the subdomain www.example.com with the CNAME to xxx.cloudfront.net.
I can't directly configure www.example.com with the CNAME in hosted zone 1 for various reasons, including that the CNAME is always changing and the person controlling the CNAME only has control over zone 2.
So the full chain looks like this:
User types in www.example.com, they get NS hosted 1 records. In that zone, the record for www.example.com points to Hosted zone 2 records. In this zone (which was created with apex example.com) the record for www.example.com is a CNAME to the proper endpoint.
My question: will any DNS resolvers mistakenly cache the NS from the second zone as apex domain records? Obviously, I want those NS accessed only for the www.example.com records. If example.com NS are mistakenly thought of as in hosted zone 2, there can be a lot of issues.
If this is the case, is there any way to make sure to dns resolvers that the apex domain nameservers are zone 1, and zone 2 records are ONLY for www.example.com, even though they were created with the example.com apex domain?
I understand that there are other ways to do this (CNAME to sep domain, etc) but for logistical purposes (for now) I am only interested in setting the NS directly for the www subdomain.
Thanks in advance.
so I am looking for a way to point records of existing domain registered on Route53 but managed by Netlify DNS.
I want to point the records to a different netlify url if possible but it will not allow me to edit the domain. Maybe what i am trying to do is not possible but here are some images to give an idea
this is netlify
this is route 53
I want to once again point my url.com to a different url then what is currently being used.
Note: I work for Netlify and have solved this problem for other customers in the past.
You cannot have DNS managed by route53 and ALSO set NS records pointing elsewhere for your main domain, or at least, I've seen that fail several times for folks trying to use Netlify's DNS hosting. You need to instead set the nameservers at your registrar to point to Netlify's nameservers. Netlify only has the capability to host DNS for domains (not subdomains), so if you are attempting to delegate a subdomain to Netlify, that will also fail.
You'll be able to tell you've done this right when the SOA record for your domain points to Netlify's nameservers. Below is an example query that demonstrates that NS1 is the delegated-to authority:
$ dig -t SOA fools.website
[...]
;; QUESTION SECTION:
;fools.website. IN SOA
;; ANSWER SECTION:
fools.website. 3600 IN SOA dns1.p03.nsone.net. hostmaster.nsone.net. 1543948999 43200 7200 1209600 3600
[...]
For example, when I buy a domain from GoDaddy and I setup up my own DNS server, the first thing is to change the NS record on GoDaddy panel. But the NS record can only be in domain format.
How can I set my domain to use my own DNS server without any others?
For example:
You create an A record for your server ns.mydomain.com -> xx.xx.xx.xx
then you point the NS record to ns.mydomain.com
I don't understand how this works. I have a domain registered at domainhoster X and a VPS at hoster Y. Since a week I am using the follwing DNS settings at my domainhoster X:
A RECORD (pointing to my server IP)
NAMESERVERS from my domain hoster
Now I registered on Cloudflare and added my domain. They told me to delete the domainhosters name servers and use their instead. Okay.
But: Do I have to delete the A RECORDS on at my domainhoster X, too and use only the A records entries on cloudflare?
If you change the NAMESERVERS of your domain to Cloudflare, your domain will follows the A RECORD rules on Cloudflare.
So you can but you don't have to delete the A RECORDS on your domainhoster X.
Only the A RECORDS changes on your Cloudflare DNS settings will have effect.