Questions tagged with Amazon Route 53
Content language: English
Sort by most recent
Route 53 will not load
Is there some new trick or way to manage Route 53? I can not get the management console to load. The page just spins and says it is waiting for some analytics site a2z.com. Would be nice if I could access route53. Anyone know how? You use to just search for route 53 click the link and it would work. Now it just gives you a blank white page. I have left it run forever and never shows anything no access and apparently since I have a free account this is the only option to see if anyone can help fix this. now it says waiting on phd.aws.amazon.com so apparently it is still doing something but who knows if it will ever display anything its has been several minutes. I noticed this last night and thought I would try again today from different computer. Logged back in and still same issue. This issue occurs both on my pc and my mac and in chrome and firefox. Holly cow after 5 minutes i think it finally loaded.
DNS address could not be found
Hello, I am facing a problem where my website’s DNS address cannot be found. What I have done: I have purchased a domain through Route 53 and use S3 buckets. I have followed this guide https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html#website-hosting-custom-domain-walkthrough-domain-registry and everything was followed. The provided website endpoint works as I can see my website and it functions correctly. The hosted zone is set with the guide and it has 4 records. 2 that get generated (haven't been touched) and 2 for my domain and subdomain. The record names and the bucket names match. The value/route traffic to the NS record name is: * ns-1971.awsdns-54.co.uk. * ns-506.awsdns-63.com. * ns-769.awsdns-32.net. * ns-1249.awsdns-28.org. The name servers of the domain are the same * ns-1971.awsdns-54.co.uk * ns-506.awsdns-63.com * ns-769.awsdns-32.net * ns-1249.awsdns-28.org (They were not but I changed them) When I try the test record without entering enting in record name the DNS response code shows No Error, however when I type in the exact same name in the record name I get Non-Existent Domain. So basically I have no idea where to go from here, please help.
Reverse DNS with BYOIP
Hi there, We have a couple of BYOIP pools we've imported into AWS and need to set up reverse DNS. For all of the IPs we allocate from that pool the "Update reverse DNS" option is disabled. The IPs have A records and the option is available for all of the other elastic IPs. Just wondering how we set up reverse DNS for these BYOIPs? Cheers
Route53 redirecting ServiceNow Instance directly to ServiceNow.com
I have a hosted zone set up in AWS route53 (labs.mycompany.com) and a Simple CNAME record inside that hosted zone (servicenow.labs.mycompany.com) and have configured it to redirect to our ServiceNow instance (dev12345.service-now.com) but rather than going to the instance it is redirecting to servicenow.com directly. I did a DiG and the DNS record appears to be accurate and fine. I tried a curl and and I'm guessing the redirect is from http to https which I believe is standard, I get SSL errors when trying http which is to be expected. I can only assume at this point that service now must be doing some kind of domain filtering at the load balancer and the website I'm getting redirected to is just the default target when no patterns match. How do I work around this so I can redirect our URL directly to our servicenow instance? Thanks
Route 53 Alias problem
I have a type A record and I would like it to alias another DNS record that is pointing to a CNAME, but an error occurs. Would there be any way to adjust this redirection? How is today: domain.com A ip.... www.domain.com CNAME name... I'm trying to solve the problem of multiple hops to reach the site. The website is hosted on an aws instance. Error: (InvalidChangeBatch 400: RRSet of type CNAME with DNS name domain.com. is not permitted as it conflicts with other records with the same DNS name in zone domain.com.)
My domain (S3 bucket linked to Route 53) returns "the server where this page is located isn't responding". Help please.
I obtained my domain from google domains, I have contacted them and they saw everything is connected correctly and stated there is nothing wrong on their end. I have gone through various stack overflow forums and the AWS documentation and it looks like everything is connected correctly, but for some reason when I use my domain the search engine just returns "the server where this page is located isn't responding". I am not sure what I am doing wrong but I started this process over a week ago and I cannot seem to find the solution.
Personal Domain with AWS beanstalk
I have a personal domain, and I would like to connect it to an AWS Beanstalk instance, I have followed the steps in the AWS Route 53 documentation but I don't know if I have to do anything else. It doesn't work for me. I have created an "A" type record and directed the traffic to the Beanstalk instance. Can somebody help me? Thank you
Old S3 and CloudFront assets are gone but causing issues
Quite some time ago I created a static website using S3, CloudFront, Certificate Manager and Route 53. I needed to make a change and all of these assets are no longer listed when I log into my console. I'm using a root account so it's not permissions. FinallyI decided just to rebuild the instances but as I try to associate the certificates, associate with CloudFront and update DNS I'm getting conflict errors. As an example if I try to associate my new CloudFront instance to a www CNAME I get "One or more of the CNAMEs you provided are already associated with a different resource." What am I to do? I somehow need my old distribution (d3s67m8gw85ues.cloudfront.net) which I can't see in my instance to become visible to me. Any help, insight appreciated.
Why do the CDK APIGWV2/Route53 docs say generate an A record rather than CNAME?
Problems with MX records
I have just recently transfer my domains and hosting them to Route 53. I am using lightsail instance for my website. I am keeping the email for my domain in the old hosting, Siteground. I have added the 3 MX records pointing to siteground before transferring the domain to Route 53. The transfer was completed last Friday and changed the DNS zone as the documentation for the domain but keep the MX records as they were. A part of having bad requests and website down since I migrated the website last Saturday, I can't send or received any email since last night. I did the DNS records in Route 53, and after migrating the website to a lightail instance last Saturday I created a DNS zone in lightsail and added the DNS records in there too. Somebody can tell me what could be the cause of that. There's a conflict if you kkep DNS records in Route 53 and Lightsail DNS zone? Shall I use only Route 53 hosting zone or lightsail DNS Zone? Could be that also the cause of the constants bad requests and website down all the time? Thanks