It's been couple of days that I transferred my domain name from one AWS to another--dev environment to production. The problem is, the domain name isn't showing up in any DNS (Amazon or Google). I'm pretty sure I've configured the hosted zone correctly.
I'm also trying to verify SES which is failing and I also set MX records (Gmail) which don't work. The MX records and SES were set couple of days ago. Additionally, I created an A record to point to a elastic load balancer DNS name.
Any suggestions on what might be the problem? It's been couple of days and from past StackOverflow posts as well as past experience, DNS propagation on Amazon's server doesn't take more than 15 minutes.
EDIT:
Here is a timeline of events which can provide more information:
I had a domain abc.com on AWS account user1
The domain was transfered to AWS account user2
As of right now, the following hosted zone is created on user2's account:
The one thing this record set is missing is a CNAME to the load balancer which I had setup when the domain belonged to user1. However my understanding is that an A record should be good enough and it was a mistake on my part.
I'm using Windows and so I've flushed my DNS. I've tried looking up using AWS's DNS servers and Google's DNS server and nothing.
C:\>nslookup abc.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find abc.com: Server failed
It's been a couple of days since the domain was transferred. MX records were something I setup immediately and so I haven't gotten an email. If the DNS doesn't have any clue about the domain name, something must be wrong.
NOTE: The domain name is obfuscated to abc.com.
As suggested by #michael-sqlbot, the name servers were different in the console and hosted zone. I updated the name servers to the NS of the hosted zone. I see DNS propagation.
Related
I have a Route53 public hosted zone containing the normal CNAME/A/etc records for using an S3 bucket to host a static website, yet "nslookup" on these records fails, and I don't know why.
The domain remains unavailable on the internet, presumably because these DNS records fail lookup.
One of the AWS troubleshooting guides recommends using "nslookup" to check the hosted zone records, but it doesn't say what to do if it does fail.
My question specifically is : since "nslookup -type=A my_domain" fails for one particular hosted zone, what can I try to resolve it?
I can see the records there in the hosted zone.
(I have another hosted zone which works fine - it uses a S3 bucket to host a static website. The website is publicly available and "nslookup" on the hosted zone records succeeds. I've tried to make the troublesome hosted zone equivalent to the working one, but to no avail.)
I already:
confirmed the hosted zone is public.
confirmed the NS records of the hosted zone match those of the registered domain
tried ipconfig /flushdns
The NS and SOA records do exist, they were auto-created by AWS (are clipped from the screenshot).
Edit:
The response from nslookup is:
Server: cache1.service.virginmedia.net Address: 194.XXX.X.100
*** cache1.service.virginmedia.net can't find bXXXXXXXXXXe.com: Server failed
Credit to kdgregory who got to the bottom of it, "nslookup" was not working because of some config with my ISP/router, the relevant comments are repeated here:
"This appears to be a problem with cache1.service.virginmedia.net. I tried looking up my personal website using it, waited for what seemed like 30 seconds or more, and got the message "connection timed out; no servers could be reached". My next guess is that Virgin Media is your ISP, and your router is configured to use their nameserver by default"
"You can try another nameserver, such as Google or CloudFlare, to verify that your hosted zone is set up correctly. Run nslookup without any command-line arguments, enter server 8.8.8.8 as the first interactive command (this is Google's service), then enter your hostname as the second command. Ctrl-D or Ctrl-C to exit"
I registered domain with AWS and set Hosted Zone.
inside the hostedzone i have NS with 4 records and SOA as a record type
I added A record type and point it to EC2 public IP.
in browser i can not get response when type domain name.i got "This site can’t be reached"
search here and some people advice to check NS with dig command.
dig command answered when i run in on Ec2 Ubuntu command but didn't get response when run it on my laptop.
I have other sites on roure53 but new one doesn't work.
any thought?
How did you registered the domain? Did you purchase it from a website and paid for it?
From what you said, it seems the FIRST thing you did was creating a Hosted Zone in Route53. Let me explain.
Usually when we purchase a domain from another website, after paying for it and everything we will need to tell the Domain Registrar to use the Name Servers and input a value like ns1.abcdomain.com and ns2.abcdomain.com . The purchase of a domain name usually comes with a free DNS service, so it will already have a valid name servers defined.
If my guess is correct, you created a hosted zone in AWS Route 53 without actually paying and registering a domain with a registrar (AWS is also a registrar). Therefore the domain only exist in AWS world because you created a Hosted Zone.
This explains why running dig on your EC2 provided the expected IP, because somewhere along the line the EC2 reaches AWS internal Route53 DNS service before reaching the public internet for DNS result.
If you indeed paid AWS something like $12 to purchase a domain, you might have misunderstood their interface (which can be confusing sometimes) and missed appointing Route 53 to be the domain's Name Servers.
I've got a web applicaiton set up on elastic beanstalk. I've a domain on route53, and I've followed the guides more or less here:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html
The URL to the webapp works fine, but the DNS is not pointing me to it.
To be honest, I'm not sure where to even begin looking at how to fix this. I've tried to use the 'Check response from Route 53' feature and I can't see anything out of the ordinary. I've attached a lot of pics.
Any idea?
Please see here for the images, I couldn't upload them here. I kepy getting format errors.
http://imgur.com/a/NwCbb
******update*******
Updated, new hosted zone configuration:
******update*******
The name is still not resolving. I've added an A type record set and selected the elastic beanstlak as the alais.
******Answer*******
Credit to imperalix for this.
Amazon registered the wrong name servers for my site.
I needed to go to
https://www.whois.net/
and search for my www.thetellyourstory.com
I got the values for my name server there:
Name Server: NS-1487.AWSDNS-57.ORG
Name Server: NS-187.AWSDNS-23.COM
Name Server: NS-1891.AWSDNS-44.CO.UK
Name Server: NS-802.AWSDNS-36.NET
Then, go into route 53 and update the name server values:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
It's important to update the name server values only as above. You can edit them directly from http://imgur.com/a/a41z2 here but it does not update the values.
It looks like your registrar, Amazon, has the wrong name servers configured [1]. I compared your whois information with your screenshot. I would recommend updating your name servers[2] for your domain to match what your zone has configured.
Update your registrar to (this is from your screenshot of Route 53 DNS):
ns-1487.awsdns-57.org.
ns-187.awsdns-23.com.
ns-1891.awsdns-44.co.uk.
ns-802.awsdns-36.net.
Your Route 53 DNS configuration look fine[3].
$ whois thetellyourstory.com
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
http://digwebinterface.com/?hostnames=www.thetellyourstory.com.&type=&useresolver=8.8.4.4&ns=self&nameservers=ns-187.awsdns-23.com
Change the NS record to just tellyourstory.com, i.e. remove the "www." from the name value.
Delete the CNAME record with the name cname.www.tellyourstory.com
Change the A record www.tellyourstory.com to a CNAME record. This record doesn't need to be an alias. It just needs to have the value of your elastic beanstalk app.
How long ago did you register this domain name and create these records? For a new domain name it can take 24 hours or so for DNS records to start resolving.
I've been trying for months to verify my domain with Amazon Web Services so that I can use Amazon SES to send emails. Verification fails every time. I've retried about 35 times. Each time it fails.
I've added a TXT record to my DNS. It looks like:
When I run:
nslookup -type=ns redmatterapp.com
I see:
redmatterapp.com nameserver = ns-1546.awsdns-01.co.uk.
redmatterapp.com nameserver = ns-692.awsdns-22.net.
redmatterapp.com nameserver = ns-1471.awsdns-55.org.
When I run:
nslookup redmatterapp.com ns-692.awsdns-22.net
I see:
Server: ns-692.awsdns-22.net
Address: 205.251.194.180#53
Name: redmatterapp.com
Address: 52.27.95.103
When I run:
nslookup -type=TXT redmatterapp.com ns-692.awsdns-22.net
I see:
Server: ns-692.awsdns-22.net
Address: 205.251.194.180#53
*** Can't find redmatterapp.com: No answer
Shouldn't I be able to see the TXT record?
You're creating the DNS record in a place where nobody but you can actually see it... on a set of name servers that you aren't actually using to host the DNS for this domain.
Your domain is evidently registered with Register365, but your authoritative name servers are actually AWS Route 53 name servers (e.g. ns-692.awsdns-22.net).
Any entries you make in the registrar's DNS record management console will have no effect at all if the registrar's DNS servers aren't the ones your domain is actually using... and that appears to be the case here.
Registrars have, in my opinion, confused this issue for many people by bundling free authoritative DNS hosting with paid name regstration services, even though these are rightfully two independent service offerings.
At some point, you switched your DNS hosting over to Route 53, and for this reason, Route 53 is where you need to create this new record. In the Route 53 console, find the Hosted Zone for this domain with matching name servers, and add this record there.
Your nslookup should start working as expected and SES should have no trouble validating your record, after that.
In the interest of not confusing future readers, the reason this entry goes in Route 53 is not because of any necessary connection between SES and Route 53. The fact that these are both AWS services is coincidental. The reason this is the fix is simply because Route 53 is who you have already -- at some point in the past -- chosen as your authoritative DNS hosting provider.
I have registered a domain name with Amazon Route53 and I'm trying to link it to an EC2 instance. I'm unable to do this successfully. I have read documentation many times over, I have looked at many tutorials online, I have read many stack overflow answers. I still haven't been able t figure it out. Help will be greatly appreciated.
What I have done so far:
Launched EC2 instance and installed LAMP stack. I'm running a web app on the instance.
Associated an Elastic IP to the instance and I'm able to reach my web app using this IP address.
Registered domain name with Route53
Created a Hosted Zone with the same name of registered domain
Created a Record Set with the following info:
Name: example.com (of course not literally, I have my domain name here)
Type: A - IPv4 address
Alias: No
TTL(Seconds): 300
Value: Elastic IP of EC2 instance
Routing Policy: Simple
This is the point at which I am stuck. When I run nslookup example.com DNS server name in terminal I get the desired response. Running dig domain name, as expected returns no answers. How do I finally connect the Hosted Zone to my domain name to get the latter pointing to my EC2 instance?
Documenting the solution as an answer. It sounds like you got everything correct except hooking up the hosted zone Name Servers to the domain name. This is done via NS Records. When you create a new hosted zone, it automatically assigns you Name Servers. To link the two together, you need to enter the NS records under the "Registered Domains" area.
1. First get the NS records from your hosted zone
2. Copy those records to the appropriate domain under "Registered Domains".
Note: NS Record TTL (time to live) can be as high as 72 hours (rarely), so it could take a significant amount of time for the change to be reflected in a lookup tool like dig (or browser).