I am having difficulties getting my domain to point to my EC2 properly. I searched through a few third party guides online, and got slightly swamped in the official AWS documentation, but despite this I still cant get it to work.
Ive have Route 53 set up like this:
Type: A
Value: ??.??.??.?? (IP address)
Type: NS
Value: ns-1403.awsdns-47.org.
ns-1696.awsdns-20.co.uk.
ns-632.awsdns-15.net.
ns-431.awsdns-53.com.
Type: SOA
Value: ns-431.awsdns-53.com.
awsdns-hostmaster.amazon.com
And on my domain host I have the DNS Records set up like this:
Hostname: www
Type: NS
Value: ns-1403.awsdns-47.org
ns-1696.awsdns-20.co.uk
ns-632.awsdns-15.net
ns-431.awsdns-53.com
I think I am doing something fundamentally wrong. Firstly Im not sure if I got the Hostname part right on my DNS records. On the site it says .domain after the input box for the Hostname, which makes me think its a sub domain specifier. Am I right in thinking the # symbol works for no subdomain? (i.e. domain.com instead of www.domain.com)
Secondly should I remove the NS record set from Route 53, as its already specified in the DNS Records on the domain host?
Many thanks
There are two missing pieces here: telling your registrar to use Route53 instead of their own NS servers, and telling Route53 about your EC2 instance.
First, you need to set up your registrar. In this step you're telling the registrar to tell the global DNS system to look at Route53 for information about domain.com. Here's a quick tutorial for Namecheap and here's one for GoDaddy. Other registrars are similar, just google for YourRegistrarHere assign nameservers.
Second, to tell Route53 about your EC2 instance you should set an A record for domain.com within Route53 pointing at the elastic IP address that your EC2 instance is assigned. You should also create another A record for www.domain.com pointing at the same IP.
For your second question, as soon as you set up your registrar correctly the interface for creating records should just go away. You'll be managing all of your DNS records through Route53 instead.
Related
Recently, I just purchased a domain from AWS by using Route 53. The problem is that I want to point this domain to a wordpress website that lies in Vultr host, but even thought I changed the NS record on Route 53 to Vulture's and test it by using https://www.dnswatch.info/, it still cannot open my website when I enter new domain to browser. I got little knowledge when it comes to DNS so please help ..
This is Vultr's DNS setting
and Route53 setting (I have changed the sensetive info)
I believe the issue here is you are attempting to add the Vultr Nameservers as NS records in Route53. So, Route53 would still be your primary nameservers.
Instead you want to specifically change over the primary Nameservers / glue records (separate UI / settings area than DNS records). See the final section on this page for details on how to do this -
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#updating-name-servers-other-dns-service
I created a domain at freenom.com
https://imgur.com/a/ClaXVLX
which points to my app at Digital ocean droplet.
and next day I created this domain I tested and it works.
that domain is 1) at printscreen above.
Now I want to create several subdomains, as I know that is possible to make:
site.com - domain
dev1.site.com, dev2.site.com - subdomains
But I do not know what must be entered in fields 2) and 3) ?
When I tried as at printscreen above I got error :
Error occured: Invalid value in dnsrecord
Which are valid values ?
Thanks!
A domain name (for use as websites etc.) should point at an IP address. There are several kinds of DNS records. Records for pointing at IP addresses are A records, as you have in 1). Other kinds are MX records for mail servers, for example.
If you want to create a subdomain, you want to create another A record, so simply choose A for the "type" field.
Alternatively, if the IP is the same as an existing record, use a CNAME record which points to another record, e.g.
Name Type TTL Target
dev1.site.com CNAME 14440 site.com
This says that dev1.site.com should use the same record(s) as site.com, so if you ever update the A record of site.com, it will automatically apply to all subdomains too.
I found the way to
add two A record
A www.dev2 IP (same ip of your original website)
A dev2 IP (same ip of your original website)
Setup 2 subdomains on the Freenom DNS:
The CNAME record type does not accept a IP number.
For the subdomains, use a CNAME, but make the target the # sign, which represents the root domain.
To be clear, this will make both subdomains point to the IP address of the A record you specified for the root domain.
If you want the subdomains to point to a different IP, then use an A record instead of a CNAME record.
We are running BIND 9.9.7 on Centos 6.5 and for a long time I have been creating "hostless" DNS entries so that sites work with or without the www.
Eg:
www IN A 192.168.1.1
domain.com. IN A 192.168.1.1
However, our client wants to use a CNAME record to a cloudfront host and the "hostless" entry doesn't work as a CNAME record.
In fact, it more than doesn't work, BIND won't even load the zone file. The error is
"failed: CNAME and other data"
domain.com. IN CNAME host.cloudfront.net.
www IN CNAME host.cloudfront.net.
It will load and resolve fine without the domain.com entry. I have tried a few variations, but nothing seems to work. including "", "."
Can anyone tell me the correct syntax for this entry?
There is no correct syntax for this (and it is not BIND specific, it is a side effect of RFC1912 which states that A CNAME record is not allowed to coexist with any other data.
Detailed explanation: Why can't a CNAME record be used at the apex (aka root) of a domain?
Some DNS providers might offer workaround hacks.
Ok, in a nutshell, for my own reaons, I am trying to "build" a solution that extracts my DNS from the location / company where my webserver is located. I need to be able to make DNS changes on the fly for my domains. I have nameservers set-up for the webserver, on the webserver. I basically want to know if I can point my domain registration DNS details, to lets say, a DYN.com dynamic DNS address, and have that dynamic address setup to just forward all traffic onto my nameservers on the webserver.
This way, I can change the dyndns "pointer" if you will, to any other webserver/nameservers immedietly should the need arise.
P.S. I know a dynamic address probably won't work, and If I have to go for a paid up service with DYN, thats fine, but I don't want to create all the records on DYN. I just want it to forward any requests to the actual ip of the name server on the webserver.
I.E.
Domain NS1 -> Dyn.com Record 1 (no specific domain records) -> ns1.mywebserver.com
Domain NS2 -> Dyn.com Record 2 (no specific domain records) -> ns2.mywebserver.com
Can this be acieved, if not, do you get what I am trying to do, and are there other ways of doing this?
I ideally don't want to create a dedicated linux VM somewhere to manage the DNS.
Thanks in advance.
I think my other question, posted after this one, solves this question.
BIND . Registrar says it cant find the nameserver. nslookup shows the domain is being handled by bind
Cheers
I have a server that already has a domain, lets say mysite.com but i want to put another site on it with the domain mysite2.com.
So my questions are, how do i set up the nameserver settings.... My first domain i have listed
ns1.mysite.com
ns2.mysite.com
So would it work if i used:
ns1.mysite2.com
ns2.mysite2.com
for my new site?
Also, i have to set up "glue records". These are the ns1 and ns2 from the nameserver and provide the ip of my server. So for the mysite2.com would i use ns1.mysite2.com and then the ip would be for example 111.111.111.111/MYSITE2 ? Because the glue record for the first site is just 111.111.111.111.....?
Hope this isn't to confusing, i'm just new to this stuff and want to understand it a bit better and i don't want to mess my original site up in anyway.
thanks for the help.
Your DNS records don't have to be within the same domain as the one they host. If you are running your own DNS servers, they can live inside your primary domain. But if you're using another DNS provider like zoneedit.com or easydns.com, just use the hostnames they provide.
"Glue records" are the NS pointers that let the root servers find the DNS servers for a particular domain. For example, there might be:
mysite.com NS dns1.example.com
mysite.com NS dns2.example.com
mysite2.com NS dns1.example.com
mysite2.com NS dns2.example.com
Note that this is entirely different from where your domain's web site is served. For that, you just configure the DNS for each of these domains so that the IP address for the "www" host (and probably the domain itself) points to the same IP ... then you read your web server software's documentation on how to set up "named virtualhosts".
Are you clear on the distinction between DNS hosting and web hosting? If not, I can go into more detail.