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?
Related
I want to know how can I redirect my website to another website (through domain name or IP address) using AWS Route53.
What I have done so far is,
1) I have bought a domain name.
2) I have generated AWS Route53 Name servers (NS) for the website and registered these NS on the domain name provider.
Now, suppose my website name is thisnewsite.com and I want that when users put thisnewsite.com or www.thisnewsite.com on browser, they should be redirected to
1)some other website, for example, www.flaticon.com, or
2)some IP address like xxx.xxx.xxx.xxx, or
3)some IP address with port like xxx.xxx.xxx.xxx:xxx
What is the Route53 method to do this?
1) For URL forwarding, see this answer: https://stackoverflow.com/a/14289082/902751
2) For IP redirect, create a record set of type A - IPv4 address that maps your host name to your IP address. This is an example (for EC2, but it will work for any IP): https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-ec2-instance.html
3) For IP redirect with port: Route 53 cannot do that. In fact, DNS in general does not care about port. It only maps domain names to IP addresses. A potential solution would be set up a proxy that would redirect your request from port A to port B.
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'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 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
I struggle to connect my domain to my ec2 instance, although I have read every post on the internet i could find about the subject:
I am using Route 53 to route my domain to an Elastic IP, which is assigned to an EC2 Ubuntu 13.04 instance. nslookup for the domain from outside shows the Elastic IP address, but returns Server UnKnown.
My setup is as follows:
Domain All four Route 53 delegation set entries added as nameserver,
DNS lookup shows everything is distributed and fine
Route 53: A record sets for domain.com and *.domain.com, pointing to
the Elastic IP
Elastic IP: Assigned to the EC2 Instance
EC2 Instance: Ubuntu 13.04 with LAMP (MySQL disabled), vHost set for
*.domain.com and enabled, added 127.0.0.1 domain.com to etc/hosts file, everything restarted and set up
Entering the Elastic IP or the direct Instance IP works just fine, only use of domain returns "Cannot resolve hostname".
I would really appreciate any help on this.
The EC2 instance and Elastic IP are fine, or else you wouldn't be able to connect with the IP address. The problem is with DNS.
I don't understand how DNS lookup can show everything is fine, but you get "Cannot resolve hostname". That's saying that your local computer cannot convert the name you've assigned to an IP address. That means something is wrong with DNS.
Are you sure that you've registered your name servers with your registrar correctly? You said that DNS lookup says things are fine. If so, then the problem must be in Route 53.
Are you using * as a host name in Route 53? If so, replace it with a simple word (like www) and see if that works.