Questions tagged with Amazon Route 53
Content language: English
Sort by most recent
getting DNS_PROBE_FINISHED_NXDOMAIN with AWS amplify and route 53 with an externally registered domain.
I'm hosting my app on Amplify, I have gottten the cloudfront address and added it to route 53 in a newly created Hosted zone. I then added the new nameservers in my domain providers portal.
When I visit the site i get the error : "DNS_PROBE_FINISHED_NXDOMAIN". I've tried clearning cookies, caches, resetting router - everything but it doesn't work
i tested the records on route53 and it found no errors.
Any help would be much appreciated
We created two route53 zones recently and created corresponding NS records at provider where we bought that domains. For some reason domains are not resolving from different places. For example: from my personal laptop it started resolving only after flushing cache on https://1.1.1.1/purge-cache/ page (I’m using 1.1.1.1 as my DNS server), in our Kubernetes cluster domains are not resolving correctly event after recreating coreDNS pods, the same problem exists on few more laptops/PCs, they still resolving records from our route53 zones to IP address that are assigned to root domain.
I’m supposing that some DNS authorities still caching old NS records for these zones but they were created 4 days ago, so all that records should be refreshed
Fllowing the following tutorial:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html
I registered a domain using AWS, my domain is visas-easy.com.
After that, I created an S3 bucket(visas-easy.com) static website and another bucket for the subdomain(www.visas-easy.com).
S3 bucket works fine with url: http://visas-easy.com.s3-website-us-west-2.amazonaws.com/
Then I created a hosted zone for both S3:
Record name Type Routing policy Differentiator Value/Route traffic to
visas-easy.com A Simple - s3-website-us-west-2.amazonaws.com.
visas-easy.com NS Simple - ns-1171.awsdns-18.org. ns-627.awsdns-14.net. ns-375.awsdns-46.com. ns-1618.awsdns-10.co.uk.
www.visas-easy.com A Simple - s3-website-us-west-2.amazonaws.com.
When I try to go to the site(http://visas-easy.com, www.visas-easy.com, http://www.visas-easy.com, visas-easy.com), result is:
This site can’t be reached
Check if there is a typo in www.visas-easy.com.
DNS_PROBE_FINISHED_NXDOMAIN
I deleted my browser cache and tried 3 different browsers (edge, safari, chrome) with the same result.
Looking to build a 3 tier application web application (not serverless) for lab purpose. I plan to leverage services in the following order: User > Route53 > ALB > EC2 > RDS, will integrate S3 in the architecture as well. I tied to boring default template I can use out of the box with wordpress. So I was wondering if you may point to a not so boring web app i can use in my architecture. For example, ride, dental or any other interesting template I can use.
Thanks in advance :-)
I created a static website by using S3 then I bought a domain name (same as my bucket name) and then routed the traffic to that website by using Route 53.
I followed these two guides in order to accomplish this:
1. [https://aws.plainenglish.io/how-to-publish-your-website-on-aws-for-beginners-e6a81da30d8b] (S3 stuff)
2. [https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/RoutingToS3Bucket.html] (Route 53 stuff)
Everything worked fine for like a month. Now when I visit my website it says "This site can’t be reached". I didn't make any changes to any settings.
Can someone explain to me what's going on and how I can fix this, please?
I go to https://us-east-1.console.aws.amazon.com/route53/home#DomainListing:
Unlock my 3 domains. The domains are .com domains.
Then I click on the button "Get code" next to the text "Authorization code" I get the following message in a popup
"Sorry, but an unexpected error has occurred while getting your auth code. Please retry again. See system status for more information on current system status."
I have tried several days now. As far as I can see there is nothing under system status. I wasn't planing on buying a support plan to solve this one.
I register my domain in Route 53, and create hosted zone by myself. Then i register for my certificate but it still pending after 2 days after i created record to my route 53 dns , i need some help.
I can't get a certificate even though I create cname type record.
Status "pending validation".
Can anyone help?
Does anyone know what reasons for a domain that fails to renew.
"Domain renew failed"
we had three similar domain example.com, example.net and example.org. They all seemed attempted to renew at the same time with only the .com and .net renewing with success.
We got this email with a no reason on why it failed.
"Dear AWS customer,
We weren't able to automatically renew registration of the example.org domain.
This happened for the following reasons:
We apologize for the inconvenience. For more information, contact Amazon Web Services Customer Support.
Regards,
Amazon Route 53
"
More details: This is a "subaccount" from our University's main account.
This has never happened before.
As I write this post, i notice it attempted to renew again but this time it was successful. Just wanted to ensure we understand why it occurred now.
-jason
From where does Route 53 Resolver get the value for a DNS query that it needs to resolve? Is this from the records that you define in a hosted zone?
Hi,
I have a domain name registered with Route53 (say its X.com). The hosted zone has CNAME records for my SSL certificate for the same domain from ACM. However, when I launch my Elastic Beanstalk instance (I have a A record pointing to my EB environment) and go to my domain name I initially get the following error:
Your connection is not private
Attackers might be trying to steal your information from X.com (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
This server could not prove that it is X.com; its security certificate is from *.Y.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
After a few mins I can reload the page and everything is fine. Is this to do with delays in propagating the certificate? Or is something else going on?
Thanks
Hi,
I have a PostgreSQL RDS instance (subscriber) that lives in the same AZ and VPC as an EC2 machine with PostgreSQL (publisher). I established logical replication subscription against the publisher about a month ago using a CNAME DNS that points to the EC2 DNS name. The publisher is restricted to only allow access from private IP in the VPC and this worked up to three days ago where it suddenly stopped. I find no events that indicate what happened but the cause is clear - the DNS name is suddenly resolving to the public IP at the RDS instance and is denied access by the publisher.
I fail to understand how this can happen and also seems against documentation. That is, I expect the DNS lookup to reliably resolve to the private IP.
Any ideas what can explain this behaviour and/or if my expectations are wrong or right?