I have such problem - Route53 does not resolve any added ( A,CNAME, ALIAS ) records to world, but resolve if i execute it with aws NS server
nslookup x.site.com ns-1583.awsdns-57.org
Server: ns-1583.awsdns-57.org
Address: 205.251.197.203#53
Name: x.site.com
Address: address
What it could be ?
Are you sure that your domain registrar is configured to use Amazon DNS servers?
Visit http://whois.domaintools.com/site.com to confirm.
Replace the site.com above with your actual domain. Then check to make sure the assigned name servers on the domain point to the name servers assigned to your domain at Route 53.
Problem was in different NS-serervers on domain registrator and route53.
Thanks for help.
Closed
Related
I want to connect a domain to my EC2 instance via the Route 53 service I set up 4 days ago. I have followed the documentation and the dig-interface shows the correct output, but when I try to access it in the browser, it sais the host can't be resolved. What have I configured wrong?
Domain: http://yet-another-blog.com
IP of the server: 52.59.214.55
Route 53 configuration:
digwebinterface.com result:
If you check the NS record of your domain it shows different nameservers than what is defined in your public zone.
It seems you created another public zone after you registered the domain or in a different AWS account.
Simply to solve this update the nameservers in the registrar to match the one in your public zone
Looks like yet-another-blog.com does not resolve because there’s no nameserver for that domain.
If you own this domain you’ll need to make sure it’s nameserver is set to target amazons name servers.
Making a public hosted zone isn’t enough.
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!
I tried to administrate my domain by AWS route53, so I changed name server in domain administrater.('Domain administrater' means corporate which I got my domain name. I have no idea how to say about that, sorry.)
I got IPv4 by Elastic IP and I regestered my domain to A record in route53, with my Elastic IP.
That was OK. I could browse my page with my domain name.
And I tried to ready my mail account with my domain name, so I registered 'mail.MYDOMAIN' in MX record and A record with my Elastic IP.
Then DNS couldn't resolve my domain name.
I had no idea to resolve that, so I removed my all my record set, I made new record set.
And I changed name server in domain administrater too.
But DNS still doesn't work.
result of nslookup is here.
$ nslookup MYDOMAIN
Server: 10.0.1.1
Address: 10.0.1.1#53
** server can't find kyttmmm.net: NXDOMAIN
$ nslookup MYDOMAIN ns-1441.awsdns-52.org
Server: ns-1441.awsdns-52.org
Address: 205.251.197.161#53
Name: MYDOMAIN
Address: 52.68.XXX.XXX #exactly my EIP
Does anyone know cause about this?
I created two public hosted zones in AWS Route53:
domain.com
sub.domain.com
In "sub.domain.com" zone I added "A" record for "test.sub.domain.com" name resolved to 10.0.1.5. I can resolve "test.sub.domain.com" name using "sub.domain.com" name servers.
> nslookup test.sub.domain.com <sub.domain.com server>
Name: test.sub.domain.com
Address: 10.0.1.5
Following instruction for Creating a Subdomain That Uses Amazon Route 53 as the DNS Service, in "domain.com" zone I added "NS" record for "sub.domain.com" pointed to the "sub.domain.com" zone name servers.
Now, when I try to resolve "test.sub.domain.com" name using "domain.com" zone name servers, I get response that name is served by "sub.domain.com" servers, but it cannot resolve to IP address. Below is example of "nslookup" response:
> nslookup test.sub.domain.com <domain.com server>
Name: test.sub.domain.com
Served by:
- <sub.domain.com server>
sub.domain.com
Does Route53 support subdomain delegation to other Route53 servers? Have I missed something in the configuration?
It seems to me that you're asking how to use Route53 NS records from within other Route53 domains?
Well, as it turns out it's very much verbatim - you go to your sub.domain.com, copy its 4 NS records (that Route53 had generated automatically when it was created), and paste them as NS records for the name "sub" within the domain.com.
(And then wait for the TTLs to expire, etc)
I think there was already one such question and answer somewhere on the StackExchange network, but I couldn't find it now.
What you are describing is how DNS works. Recursive name servers would follow the name server referral and ask the name servers for sub.domain.com to resolve test.sub.domain.com.
You can try this out by doing a dig +trace test.sub.domain.com, assuming your are delegating domain.com to the route 53 you configured in the .com zone.
In addition to Josip Rodin's answer I had to add A record to my subdomain hosted zone as an alias to my Elastic Beanstalk environment.
After this and TTL expired all started working.
I am using EC2 Amazon Web services, and also I am using route 53. My domain example.com is not resolving, I can see the website if I type elastic IP address. How can I solve this problem. Thanks in advance,
A very nicely written steps to do the config :
http://docs.aws.amazon.com/gettingstarted/latest/swh/getting-started-configure-route53.html
Because you did not add what you have done so far in the route 53, I have to ask below general question and you can verify if you have done these.
Have you created a hosted zone?
Have you added type A record in your recordset to point example.com to your EIP?
Have you created cname for your www.example.com?
Have you logged in your domain name registrar site and updated the nameservers provided by route 53?