I'm new to Amazon.
My client hosted their website www.domain.com at godaddy and
they have created the aws ec2 instance and running their Django apps in this instance.
Now they wants to use this instance for subdomain. say www.subdomain.domain.com
So I have created a record set in aws route 53 by following procedure.
Created Recordset A pointing to elastic IP
Created Nameserver (NS)
Finally added this recordset into godaddy dns files. Still I'm not able to access this subdomain. Please can anyone help here.
Are you managing DNS through AWS?
If so..
You need to create a DNS Zone for that domain.
Add the records or import the ZONE file
Take the Name Server records from AWS
Go to the domain registrar(assuming you manage this also), in this case GoDaddy!
Point the Name Server records from AWS to GoDaddy!
Related
[Internet Resolver][1]
Hi ,
How can I delete this , it been trying but I am not getting any suitable way to delete it .Thanks
[1]: https://i.stack.imgur.com/5MigP.png
If you are using amazon provided DNS in your VPC then dot (.) rule will be the default for internet resolver pointing to amazon DNS server. You can not delete this as it will be assigned to the default VPC in that AWS account. However you can override that association with your VPC is in question and you can have your custom dot(.) forwarding rule pointing to your own DNS server or another server in the internet such as 8.8.8.8. and have that rules associated with all your VPC to have DNS query resolved accordingly.
However if you are using a custom server make sure you have a system rule in place to resolve amazon owned domain name(amazonaws.com) privately. and associate that system rule with all of your VPCs.
I have transferred my domain from Google to AWS 7 days back. The transfer process has been completed in AWS. I have created a public hosted zone in Router 53 and the NS records present in Route 53 are matching with the NS records of my domain in AWS. Also created CNAME records pointed to the application load balancer.
I am able to access my domain inside AWS workspace and even dig command returns the results in my AWS workspace but not working in some machines outside of AWS workspace but when I use load balancer url, I am able to access the application so there are no issues with security group configuration.
Also no dig results when using this url https://toolbox.googleapps.com/apps/dig/
Am I missing something here? Any help is highly appreciated
The issue is resolved after disabling the DNSSEC in Route 53. I think I had not disabled DNSSEC in google before transferring the domain to AWS so it has transferred the DNSSEC with keys to AWS.
I'm trying to request a certificate using AWS certificate manager. I'm using route53 for DNS. I go through all of the steps, and use the "create record in Route53" to create the CNAME record automatically. I have double checked the CNAME record in Route53 to make sure it is the same one that ACM expects. After doing all of this, the DNS validation times out.
I have tried this multiple times with the same result. I barely know how to use dig so I'm kind of lost on how to troubleshoot this. Thanks.
I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.
Hope you are not making the same mistake :-)
When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.
I had registered a domain with Route 53 and was facing a similar issue when I deleted my website's hosted zone.
The CNAME record in Route 53 was exactly as it was in ACM (no extra strings, whitespaces, etc.)
The issue was in Route 53 - the name servers associated with the registered domain were different from the name servers associated with the hosted zone.
I fixed this issue by:-
Deleting and re-creating the hosted zone.
Replacing the NS values in the registered domain with the NS values of from the newly created hosted zone.
Creating a certificate in Certificate Manager with the domain name matching with the one specified in Route 53 hosted zone.
Creating a Route 53 record from the Certificate manager wizard (which is step 5 in the wizard)
I am attempting to setup my own email server on ec2. Also, I m using route53 for DNS. Also, I m using elastic IP to get static public IP. My question is where will i setup SPF, DKIM and DMARC records in route53 or in my bigrock control panel. My domain in hosted in ec2 instance. Any information about setting up these records will be of great help
Any help would be appreciated.
You need to go to Route 53, and to the hosted zone in question. Create an MX record for the email server, e.g. pop.myserver.com. Then just follow the doc at:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#SPFFormat
https://forums.aws.amazon.com/thread.jspa?threadID=229677
I've recently setup a new Tomcat instance on Google Compute Engine and I can access my Tomcat instance via its IP address in the browser.
I've now setup a Cloud DNS entry and had my domain registrar point my domain name to the Cloud DNS servers. However this was 2 days ago and I still can't access my website via the domain name.
The WHOIS record shows the following Name Server entries
Name Server ns-cloud-e1.googledomains.com
Name Server ns-cloud-e2.googledomains.com
Name Server ns-cloud-e3.googledomains.com
Name Server ns-cloud-e4.googledomains.com
I've also setup an A record in the Cloud DNS console based on the feedback of my domain registrar. Is there anything else I need to setup in order for all this to work?
[EDIT 1] Having a look again at the instructions provided by Google it seems the name server names they wanted me to use have changed to
ns-cloud-d1.googledomains.com.
ns-cloud-d2.googledomains.com.
ns-cloud-d3.googledomains.com.
ns-cloud-d4.googledomains.com.
I've asked my registrar to make the change in case this is the problem.
[EDIT 2] My registrar has updated my DNS records and they resolve to Google's servers. However my website still doesn't show when entered into a browser I get an NXDOMAIN error, which implies my domain doesn't exist. Does anyone have a basic example of what the Cloud DNS settings should look like? Do I need to setup A records or CNAME records?
[EDIT3] My setup is shown here (domain name and IP addresses have been faked for screenshot)
Thanks in advance.
Andy.
OK, I finally worked out the problem.
In the screenshot in my question the following changes were required.
1) Replace the A record for *.andtest.com.au with an A record for just andtest.com.au
2) Replace the www.andtest.com.au A record with a CNAME record for www.andtest.com.au which points to andtest.com.au
Now when I enter www.andtest.com.au in a browser, I see my Tomcat web page.