I'm pretty new to DNS and this is the first time trying to connect a domain name to an IP, so I'm not sure what I'm missing here. I tried connecting both the www and non www NS records to the Lightsail name servers but only the non www option seems to be working. When I try to hit www.[domain].com, I get unresolved hostname. I also added an A record in each hosted zone that points directly to the IP and I'm not sure if they actually did anything, but I can only access the site from the IP or from http://[domain].com. I appreciate any help you guys can give me, hoping its something small.
Here is an album containing my hosted zone and each zone's settings
I think you don't need to use two separate hosted zone for www and the apex domain (non-www). You can have a single hosted zone and create resource record set for www and the apex domain using CNAME or Alias records. Since you already have an A-record for example.com, in the same hosted zone you can create a CNAME record for www.example.com and point it to example.com
Regardless, for the domain not found, it could be due to the TTL.
Hope this helps.
More information:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#CNAMEFormat
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-basic.html#rrsets-values-basic-ttl
Related
i have bought a domain, for example examp.com, by hoster x.
A little bit later i have realized that aws is better for me.
I have register a hosted zone with my domain and change the NS-records by hoster x to the NS-Server from my hosted zone.
It works perfect!
But now i would like to whitelabeling my website.
For example a client have a domain abc.de and he would like to access my website with a subdomain sub.abc.de.
My idea was to create a CNAME-Record on sub.abc.de that points to examp.com.
But that not work (Not Found - The requested URL was not found on this server.).
I have read that the target server gotta know from the CNAME-Record that points to him. But i don't know how can i do that. In my hosted zone i can only register subdomains for examp.com for a ALIAS or so but not for another domain.
Can anybody help me?
If they control the domain of abc.de they are able to create the record their side for sub.abc.de as a CNAME record with the value set as your domain (examp.com).
They should never be attempting to CNAME to your NS server records, these are records for where your DNS records can be retrieved from.
Other than you providing the CNAME value of examp.com to them it is upto them to configure their DNS to target your hostname.
I've registered my domain on Route53, deleted the default hosted zone, and set the name servers to the ones provided by Lightsail. I've also set up a hosted zone in Lightsail with two subdomains: # and www. Both are A records that point to the static IP of my Lightsail instance.
The top-level domain works fine, but the www is giving an "IP address not found" error on my browser. What might be going wrong?
Turns out it just takes a while for the DNS to update.
You can use https://www.whatsmydns.net/ to check if DNS is updated.
I am currently hosting my website on amazon elasticbeanstalk and I purchased a domain from namecheap.com then I followed the steps here. On AWS route 53 I created a hosted zone and an Alias record then on my namecheap account I selected custom DNS as my DNS servers and inputted the values I got from AWS route 53. Now after 24 hours I can access my website from www.domain.com but not from domain.com. I opened up a terminal and I pinged domain.com it says "unknown host domain.com" but pinging www.domain.com works. I don't know why.
For this you need to create an another Record Set with empty name i.e. leave the name field blank and provide the value same as www.yourdomain.com (your IP address).
Please do note that both the values on WWW and non-www should be the same.
Hope this would solve your problem!
Right now our domain name and DNS are still hosted by our old provider until we make the full switch to Amazon AWS.
We run a lot of subdomains i.e. vendor.mydomain.com which were previously setup as websites on our old host. I deleted the subdomain on the oldhost and replaced it with a cname on the mydomain.com level for vendor to point to AWS, all is working well.
Now I need to add some TXT records for mailgun to verify my domain and I'm not sure where / how to do it.
Mailgun is looking for and expecting a CNAME record email.vendor.mydomain.com. I tried creating this on mydomain.com as I did for the vendor CNAME, it lets me create it but it never seems to be detected by mailgun.
I figure I could go with the configuration where I create a subdomain on my original host, but then the nameserver of my old host takes over for vendor.mydomain.com. In this scenario I'm all good with the Mailgun CNAME's etc, but I don't know how to effectively point to AWS for vendor.mydomain.com as the CNAME on the domain level no longer works.
Thoughts / suggestions welcome!
If, on the authoritative server for example.com, you have a CNAME record for subdomain.example.com, no other records on that same server can be valid for, or under, that subdomain, because the CNAME effectively blocks everything at or below itself by saying "stop, look elsewhere... specifically, look here."
Create a hosted zone in Route 53 for example.com. Note the 4 awsdns name servers it assigns to the hosted zone.
For each subdomain you need on Amazon, create 4 NS records for each subdomain on the example.com authoritative servers.
vendor NS ns-xxxx.awsdns-yy.com.
vendor NS ns-xxxx.awsdns-yy.net.
...etc., for the .org and .co.uk domains.
This delegates all lookups for that subdomain (e.g. "vendor") and all of its subdomains to the Route 53 servers, while leaving your existing servers authoritative for the records it still contains.
Then you can create records in the hosted zone in Route 53, including alias and CNAMEs as needed.
I`m currently using route53 for 2 domains that points to the same website.
Lets assume they are www.example.com and www.example.com.xx, I`ve created 2 hosted zones and maintained the configuration created by default. So, initially I had entries for NS an SOA in each hosted zone.
My EC2 instances are behind Elastic Load Balancer, so my first step was to create aliases for both domains and it naked domains, having the following scenario:
www.example.com
name type value
example.com. NS Generated value
example.com. SOA Generated value
example.com. A ALIAS to my ELB
*.example.com. A ALIAS to my ELB
www.example.com. A ALIAS to my ELB
www.example.com.xx
name type value
example.com.xx. NS Generated value
example.com.xx. SOA Generated value
example.com.xx. A ALIAS to my ELB
*.example.com.xx. A ALIAS to my ELB
www.example.com.xx. A ALIAS to my ELB
Both domains are pointing to the same ELB, where Apache configs to example.com. Then, my Django app subdomain middleware redirects to example.com(301) if request.get_host contains the .com.xx substring.
It is working perfect for both www.example.com and example.com as for www.example.com.xx, my problem is with example.com.br that never reaches my server.
I`ve already tried to make a PTR entry example.com.br -> www.example.com.br, but it was not the solution.
Anyone can point where my DNS config for this naked domain is failing?
Thank you
Firstly lets worry about example.com.br. [www.example.com.br we will take later]
Did you made changes on ur Domain registrar; so as to give DNS servers as that of Amazon ? What is the output you are getting when u do :
nslookup example.com.br
also what is the output for
ping example.com.br
Yesterday night I was able to redirect my naked domain properly, it was a bug in my brazilian provider that was dealing with the registrar. Actually, I just gave them back the control of the DNS table and took it away (returning it to route53).
Anyway, they were being used as a bridge to the registrar since I was migrating. Now I`m dealing directly with registro.br and the problem is gone.