Questions tagged with Amazon Route 53
Content language: English
Sort by most recent
Hello, I'm not a web developer. I created my AWS EB WebApp as Classic Load balancer. I'm now setting up Cloudfront distribution for CDN with a custom domain that I bought from AWS Route 53. My cloudfront is working, but it's not responding for POST request. When I read about it online, I think my aws eb webapp should be migrated to Application Load Balancer. Could you help please? - Haile
I recently transferred my domain to route 53 , created a new public hosted zone and used the same nameservers on the hosted zone to modify the name servers under the registered domain section. I created an A record and linked it to one of my app runner instances but its just not resolving. The status code of my domain is clientDeleteProhibited clientTransferProhibited transferPeriod clientUpdateProhibited. Its been over 2 week but nothing has changed
I created an Opensearch Domain using an IAM user, but after creation I can't see the created domain in the root. What is the problem.
By configuring a bation host in my network, the server in the external network can access my vpc. In this case, can I connect the domain to an external server using bation host through private hosting through route 53?
hi, Does anyone know why the private IP address of the MWAA web server keeps changing time to time? Example: i have an AWS MWAA environment and i created a DNS record in route53 against the IP address i get after running the dig command against the web server hostname, but the url stops working after few days and when i check the dig command again, i get a new IP. Any help would be great. Thanks.
R53 fails over to S3 redirected website. After the web service is restored, the normal website cannot be accessed, and the domain name access will still jump to the maintenance page.
May I ask how to solve this problem? My apache servers are placed in the east and west respectively, and ALB is set up. After monitoring two ALBs through the global accelerator to achieve load balancing, now I need to configure failover: when both servers are down, The domain name access jumps to the maintenance page. The method I use is to set an A record for the R53 hosting domain name, and the routing policy is failover to S3. S3 does not set a static site, because there is a maintenance page hosted by a third-party service provider, and it can be accessed normally. Therefore, the redirection to the maintenance page hosted by the third party is set, but the failover jumps over. After the web service is restored, it is still redirected to the maintenance page. It is necessary to clear the browser cache to access the site normally. Is there any way to use it as a web service? after normal access
I have a domain with rout53 configured to a Gmail, mail server using MX The setup has been working for a year but just recently am unable to send and receive emails, sent emails bounce back with an error: DNS Error: DNS type 'mx' lookup of getaidpharma.com responded with code SERVFAIL How do I resolve this?
How to change domain contact when contact has left organization so can't 'approve' change because no one has access to their prior organizational email account.
I purchased a domain name via AWS route 53 that is similar to example.co.uk Is it possible for me to route any traffic from example.co.uk to www.example.co.uk and if so, how do I do so? Or would I need to purchase the www.example.co.uk url from elsewhere.
Hi, I was trying to register a domain name for my association but unfortunately I have received an email says "We weren't able to register the domain name." we can't finish registering your domain. Contact AWS Support at this link Did anybody have the same problem? Kindly help to solve this issue!.
Hello, I'm trying to create a distribution on Cloudfront and S3 and use a domain outside of AWS, with route 53 I can use my domain without problems, but my question is whether it would be possible to use my domain without using Route 53. on the site that hosts my domain, since I don't have ns, it's like something is missing. I can manage to configure the cname from the certificate generated in ACM, the txt and the alias that points to the cloudFront, but I could not configure the ns. So, is Route 53 fundamental in this process?
******J**ust got the following message from AWS. Not sure what to do. As per this notice it says " ChangeResourceRecordSets" in route 53 affects this change. How and and where to upgrade TLS version for it? ******** AWS is updating the TLS configuration for all AWS API endpoints to a minimum of version TLS 1.2. In preparation for this update, we have identified TLS 1.0 or TLS 1.1 connections to AWS APIs from your account that must be updated to maintain AWS connectivity. Please update your client software as soon as possible to use TLS 1.2 or higher to avoid the risk of an availability impact. We are making this change so our customers can benefit from the enforcement and simplification of only modern TLS encryption protocols. This update will remove the ability to use TLS versions 1.0 and 1.1 with all AWS APIs in all AWS Regions by June 28, 2023. Therefore, we recommend considering the time needed to verify your changes in a staging environment before introducing them into production. How can I determine the client(s) I need to update? We have provided the connection details following this messaging to help you pinpoint your client software that is responsible for using TLS 1.0 or TLS 1.1, so you can update it accordingly. Additionally, our related AWS Security blog post  provides information on how you can use TLS information in the CloudTrail tlsDetails field. Please see the following for further details on the TLS 1.0 or TLS 1.1 connections detected from your account between February 25, 2023 and March 13, 2023 (the UserAgent may be truncated due to a limit in the number of characters that can be displayed): Region | Endpoint | API Event Name | TLS Version | Connection Count | UserAgent us-east-1 | route53.amazonaws.com | ChangeResourceRecordSets | TLSv1 | 1 | AWSPowerShell/184.108.40.206 .NET_Runtime/4.0 .NET_Framework/4.0 OS/Microsoft_Windows_NT_10.0.14393.0 WindowsPowerShell/5.0 ClientSync us-east-1 | route53.amazonaws.com | ListResourceRecordSets | TLSv1 | 1 | AWSPowerShell/220.127.116.11 .NET_Runtime/4.0 .NET_Framework/4.0 OS/Microsoft_Windows_NT_10.0.14393.0 WindowsPowerShell/5.0 ClientSync