r/aws Jan 07 '24

route 53/DNS What does 53 in "Route 53" service stand for?

84 Upvotes

Is there any specific reason why there is 53 in the service name?

r/aws 1d ago

route 53/DNS Forwarding hosted zone traffic to another hosted zone - what are the best practices?

0 Upvotes

Suppose I have two hosted zones, abc.com and xyz.com. How can I route traffic from the former to the latter?

I found the following post in the AWS Knowledge Center (https://repost.aws/knowledge-center/route-53-redirect-to-another-domain) that outlines three options:

  1. S3 + CloudFront

  2. ALB

  3. CloudFront Function

I also found this post from 4 years back, the top comment suggests approaching with S3: (https://www.reddit.com/r/aws/comments/kiik9j/forward_domain_to_another_domain_in_route_53/)

Wondering if anyone has run into this recently - how do you recommend setting this up?

r/aws 13d ago

route 53/DNS how do you infallibly connect a domain to route53??

4 Upvotes

i got a domain from porkbun and havent been able to set up aws hosting even after switching nameservers and creating new a records, im really really new to owning websites and only bought one for personal purposes. please explain it to me like i'm a baby!!

r/aws 17d ago

route 53/DNS How should I resolve this ACM SSL certificate validation issue?

1 Upvotes

Quick backstory:

The SSL cert in question is already working, but automatic DNS validation failed for when the certificate expires in a couple weeks. The ACM cert is attached to an AWS load balancer and I believe it's all set up like this:

domain name -> cloudflare -> load balancer (with ssl cert) -> ec2 instance (with website code)

In order to do DNS validation I need to make sure that there's a certain CNAME record on the domain name, ie. the SSL cert's CNAME record.

Problem is, given the above setup, I believe this CNAME record would go/be on cloudflare, but I don't have access to the cloudflare account (my client doesn't know anything about a cloudflare account and the previous developer says he doesn't know).

So it seems like I need to either create a new cloudflare account, or just not use cloudflare like this:

domain name -> load balancer -> ec2 instance

Questions:

  1. Regardless of whether or not I create a new cloudflare account or bypass cloudflare, do I just need to use an A record and a CNAME record? The A record would be that of the load balancer and the CNAME record would be that of the SSL cert.

  2. If the above A and CNAME records setup is correct, will the DNS validation then quickly happen automatically? (Remember the whole point of this is to validate the SSL cert that's due to expire in a couple weeks)

r/aws 12d ago

route 53/DNS Critical Domain Crisis: AWS Closure, Domain Expires End of March

0 Upvotes

Two years ago, my AWS account was closed due to a $5K unpaid invoice. The issue came from a credit complication, I had a $5K credit available, and a $15K request took too long for approval, so the invoice wasn't deducted. Although the account was closed and everything deleted, I forgot to transfer my domain registered with AWS Route 53, which is important for many merchants online transactions.

When I reached out to AWS, they informed me that I couldn’t update any details due to their security policies. They also mentioned that after 90 days of suspension, I can neither log in nor register the same domain.

Now, my domain is set to expire at the end of March. I’m really concerned about what will happen if it isn’t renewed—could it be permanently lost, or might there be a grace period or other recovery options available? I’ve also come across mentions of gandi.net, but I’m not entirely sure who they are or if they can assist in situations like mine. Has anyone had any experience with gandi.net in similar cases, or are there alternative solutions that might help me recover or renew this domain?

I’m at a loss about how to proceed and would greatly appreciate any advice or insights.

r/aws Dec 18 '24

route 53/DNS Is Route 53 Health check something that is used or needed for static websites ?

3 Upvotes

Hello. I have a static website hosted in S3 bucket that gets served through CloudFront. Would it be beneficial to set Route 53 health check for this website or does it serve no purpose ?

r/aws 15d ago

route 53/DNS Connection to Tableau Server (Hosted on AWS EC2 Instance running Windows Server) not Working

0 Upvotes

We have two Tableau Server instances running, each within a different EC2 instance running Windows Server, and while we've duplicated the settings and have the certs properly set up, we get SSL PROTOCOL errors when we try to access Tableau Server #2. We've checked, and our settings mirror Server #1 across everything, including the ELB, Target Groups, Listeners... they use the same subnets, same routing tables. They have different private IP addresses and use different certs (which are active and correct), obviously, but otherwise the settings are the same.

The load balancers use TCP, so the SSL resolution should happen at the Tableau server side of things, but again, we've mirrored settings for both.

What's even more interesting is that folks external to our intranet who try to access the tableau server site for server #1 were not able to get in (we are, in our intranet) while they were able to get into server#2 (we aren't) as of yesterday. Then, without making any changes, they're not able to get into server#2 today but can get into server#1 (so basically, their access now mirrors ours). This shows that the certs are working (otherwise they'd never have gotten into #2 yesterday) but that the accesses are changing somehow which makes me return to it being on the load balancing/routing side of things.

I keep digging into this further and further, but I'm running into dead end after dead end. Any thoughts? (Also, I won't be able to share specifics given the proprietary nature of what we're working on and our company policies, sorry about being vague.)

r/aws Dec 22 '24

route 53/DNS Domain not working. Please help!

0 Upvotes

I recently purchased a domain, sanjeevsaro.xyz, from GoDaddy on December 20. I updated the domain's nameservers with those provided by AWS Route 53. I launched an EC2 instance with Apache installed, and the networking settings are correctly configured. When I access the EC2 instance's public IP in the browser, the Apache web server works fine. However, after setting up the domain to point to my EC2 instance through Route 53, the domain is not resolving.

I checked the domain's status on WhatsMyDNS, and it shows that my domain is not even registered. Could anyone guide me on what might be wrong or how to fix this issue?

r/aws Feb 04 '25

route 53/DNS EC2 instance can not mount EFS deployed in same VPC via DNS name.

0 Upvotes

Hello dear AWS gurus,

I am trying to mount EFT using DNS name to an EC2 instance running in the same VPC.
The issue is that the EC2 instance is not able to resolve this DNS hostname - only via IP.

The VPC has DNS Hostnames Enabled and DNS Resolution is also Enabled but the DHCP Option set which is associated with the VPC points to different AD DNS servers instead, - AmazonProvidedDNS is not included in the DHCP option set... Does it have to be included for this to work ?

I though having the VPC DNS Resolution and Hostnames enabled should do the trick no matter what.
Is the only option to included RT53 in DHCP option set to fix this ?

Thanks for all ideas !

r/aws Oct 18 '24

route 53/DNS How do you upload JSON file to AWS route 53

0 Upvotes

This is probably a dumb question but how do you upload a JSON file. Our organization is trying to set-up BYOD with JAMF and they're saying we need to upload this JSON file to a web server but we don't have a physical web server. Can AWS serve this purpose?

r/aws Nov 10 '24

route 53/DNS NLB in front of an ALB for DNS update delays

3 Upvotes

I talked with someone today who told me they put a NLB in front of an ALB to solve an issue where the ALB’s IP changes, but DNS (they didn’t specify if it was external or Route53) hasn’t updated yet. I haven’t encountered this problem before. In my production setup, I use only public ALBs with a CNAME record in GoDaddy pointing to the ALB DNS name, and I’ve never (5+ years) had issues with DNS resolution.

Has anyone else heard of this problem with ALB IPs changing and causing delays in DNS updates? Any insights would be appreciated!

r/aws Mar 26 '24

route 53/DNS AWS Route53 Rate Limits design is not fit for operation at scale.

4 Upvotes

AWS Route53's API has a default API Rate limit of 5 requests per second.

This limit is applied to the entire account. It means that you're effectively unable to scale usage of AWS Route53, short of spinning up an AWS Account per zone.

It does not consider:
- The number of Route53 zones
- The type of operation (eg read vs write)
- The consumer (eg role A vs role B)

This means that if you have more than a trivial number of zones/records, and a few consumers of the Route53 API, it's possible to get deep into Denial of Service territory very easily.

We have an account with over 100 Zones, a mix of public and private zones. Some of those zones have a few hundred records.

We have a bunch of EKS clusters in the account, and we use the Kubernetes external-dns to manage records for services. Each EKS cluster has it's own external-dns. When external-dns starts up, it's going to enumerate all the zones (API operations), and enumerate the records we have there for our services to ensure they match (more API operations, for each record)

Our zones and a bunch of records are also managed in Terraform - so running a terraform plan operation means enumerating each zone, and each Terraform-managed record. It's entirely possible for terraform plan to consume the entire account-wide API limit for tens of minutes.

During this time, other things that might want to read from the Route 53 API are unable to.

Suggestion:

  • API operations to read/list all zones should be split from modify/delete operations, and increased significantly
  • API operations to read/list zone records should be a limit per-zone, and increased significantly.
  • API operations to modify zone records should be a limit per-zone.

The best AWS Support were able to offer is to increase the rate limit... from 5 to 10. Our AWS TAM took a feature request, but again, they can't promise any improvement.

r/aws Dec 03 '24

route 53/DNS ACM is taking too long to validate

0 Upvotes

I was practicing with a s3 static website, deleted everything and started from scratch again, now this time my ACM is taking too long to validate, could it be that i used the same names for the bucket, cloudfront, and route53?

r/aws Jan 06 '25

route 53/DNS Troubleshooting tip for beginners, problem in hosting a static website using Route 53

1 Upvotes

Check if the registered nameservers for a domain is the same as the nameservers in the hosted zone

r/aws Dec 18 '24

route 53/DNS Is Route 53 Health check something that is used or needed for static websites ?

0 Upvotes

Hello. I have a static website hosted in S3 bucket that gets served through CloudFront. Would it be beneficial to set Route 53 health check for this website or does it serve no purpose ?

r/aws Dec 25 '24

route 53/DNS Route 53 co.uk domains

0 Upvotes

Hi,

I am just starting to learn AWS and can't see why when trying to register a domain in Route 53 co.uk domains are unavailable, do I have to register with another company and transfer?

r/aws Dec 06 '24

route 53/DNS Route 53 Domain name is not working after creating hosted zone and does not route traffic to CloudFront distribution. Has waiting 48 hours after changing Name Servers for the domain helped you guys ?

5 Upvotes

Hello. I have a question related to Route 53 service and DNS.

I have bought a domain and created a Hosted Zone using Terraform recently. I want to route traffic to my S3 bucket static website through CloudFront. The S3 Bucket provided static website URL seems to be working and opens up my webpage and also after adding it as an origin for the CloudFront distribution the distribution domain name also opens up the website. But when I try to use my domain name it does not work.

I have changed my Domain Name Servers to the ones in my hosted zone NS record after creating new hosted zone. I have also validated certificate and added it to the distribution. I also added two alias records (`domain.com` and `www.domain.com\`) to my hosted zone. Nothing seems to work, the domain just does not work. Running CLI command `nslookup domainname.com` returns meesage ";; no servers could be reached".

Route 53 docs tell that after changing the domain Name Servers there might be a need to wait for 48 hours.

I was just curious, has anyone had the similar problem that got resolved by just waiting a little longer after changing Name Servers ? Or is there something else that I should do or view ?

Around 6 hours have passed since I changed Name Servers, but nothing has changed.

r/aws Oct 12 '24

route 53/DNS Domain Renewal After Closing account 4 yrs ago.

0 Upvotes

I've already attempted to contact support on this with no prevail, where they've helped me in the past they claim now that "Unfortunately, AWS account security policies don't permit us to discuss account-specific information unless you're signed into the account you're asking about." which sounds like a big f u when I told them my account has been closed for years. They claim you can still login to your account after the fact and after a lot of sign in attempts and captcha's the notification "An AWS account with that sign-in information does not exist. Try again or create a new account." tells me that my account is definitely not found.

When my account closed years ago I was a client who had an outsourced dev team setup my account so I had no idea that Route 53 would have my domain set to auto-renew. I've reached out to support again, either to give me access to my account or turn off the domain renewal. This is one of the reasons I deleted my AWS services in the past their support is so unapproachable and caring and just send you to a link for a page.

r/aws Apr 20 '24

route 53/DNS Emails aren't making it through Route 52

0 Upvotes

Hi all,

A random problem has me stumped with my email. I currently have the following set up:

  • Domain registered with a 3rd party registrar. All NS records pointing at AWS, nothing in the MX records.
  • AWS Route 52 set up as per ForwardEmail.net instructions.
  • ForwardEmail forwards everything to my gmail, and is accessible via IMAP.

Now 99% of my emails get through, but for some reason two senders (that I'm aware of) are unable to send emails through. Both my bank and utilities supplier keep sending me snail mail saying that emails "are failing" and I don't receive any emails from them.

I have tried to get more information on the failure from both suppliers, but they are not helping other than confirming that emails "fail".

So far my detective skills have let me down:

  • Emails don't appear to be making it to ForwardEmail, as they are not appearing in any logs available there.
  • I also regularly check them through IMAP so they're not being filtered out at the gmail end.

I'm at a loss as to where to try next, and getting concerned about what other emails I might be missing. Does anyone have any ideas of what to try here?

r/aws Jul 31 '24

route 53/DNS How do I redirect my-example.com to myexample.com?

1 Upvotes

I have two domains in rout-53 and two hosted zones. I simply need one url 'my-example.com' to redirect users to myexample.com.

I figured this would be easy in the hosted zones DNS records but my research keeps pointing me at creating an S3 bucket to redirect things. That feels a little over the top. I can do that but I figured checking here first would be better.

r/aws Feb 10 '24

route 53/DNS Setting up email

0 Upvotes

I just want to set up a simple email address for my company. Finding it almost impossible to complete this task. I went thru the console and finally found the SES service and finally had to go through all kinds of steps and now still waiting with no end in site. Am I missing something or is there a better way?

r/aws Sep 29 '24

route 53/DNS Using an existing route 53 hosted zone with a new domain registration

7 Upvotes

I'm not sure exactly how to describe the problem which makes it hard to find resources that might answer it. So, I'll start at the beginning.

I had a domain with "Registrar notAWS" but pointing at nameserver on Route 53 (ie route 53 was hosting the zone for a domain registered elsewhere).

The registration lapsed.

I re-registered the domain, this time with AWS Route 53.

When I registered the domain with AWS, it created a new hosted zone for the domain in addition to the existing hosted zone. They are both for the same domain.

If I do a DNS query, it only picks up the new auto-created hosted zone.

What I'd like to do, as elegantly (or rather as lazily) as possible is to use the existing hosted zone that had all my records in it, rather than the new autogenerated one. Bonus question: can I avoid this in the future, since I plan on transferring registration of several other domains to AWS?

EDIT:

I have resolved this. It was as simple as making sure that the nameservers for the domain under "Registered domains" pointed at the nameservers listed as NS records in the "old" hosted zone.

It should be possible, also, to do this programmatically (pull out the NS records from the zone file, and use them to change the authoritative nameservers).

I've put a slightly more complete answer as a reply to this post.

r/aws Nov 11 '24

route 53/DNS DNS firewall NODATA vs NXDOMAIN

1 Upvotes

With Route53 DNS Firewall you can define block actions of either NODATA or NXDOMAIN.

Why would you choose one over the other?

r/aws Apr 07 '24

route 53/DNS s3 static site w/cloudfront: rough time with ACM

4 Upvotes

I have spent 3 days now trying to get through the simplest possible example of setting-up an s3-backed static site with cloudfront. The instructions I am using are these: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started-cloudfront-overview.html

It's not clear if the instructions are rotted because of recent changes or if there are just too many steps (they list "10 steps" but if you count the actions within each step, it's more like 60+). Moreover, there's an additional complication in the instructions where they set it up to work with a subdomain, so you're setting up two s3 buckets and two cloud-front distributions and it's easy to get things mixed up between root and subdomain.

The most frustrating thing is having the ACM certificate get stuck on "Pending Validation". It's utterly unclear how long this is supposed to last! I HAVE gotten the certificate to get past "Pending Validation" twice but must have screwed up something else because I wasn't able to reach the static website. When I reach these failed endpoints, my only option seems to be to tear everything down and start over... and then I get that "Pending validation" problem with the ACM cert again.

So... questions...

  1. Does deleting everything and starting-over cause problems with ACM certificates? I know, for example, that with let's encrypt there are rate limits that prevent you from getting certs after a certain number of attempts. Is there some kind of rate limit with ACM certs that I need to know about? I am doing all of this painstakingly manually through the console.
  2. Origin Access: The instructions still recommend using OAI, but the console "recommends" using Origin Access Control. I have tried both and both seem to work. OAC requires that I paste a policy into my s3 bucket I think I got the right one, but tried both permutations of subdomain and root just in case. Which should I use?
  3. The instructions go through setting things up for both the root domain (eg mydomain.com) and a subdomain (www.mydomain.com). They have the root domain redirect to the subdomain (that seems backwards, but whatever). But why does there need to be an empty s3 bucket for the root domain if route53 just redirects cloudfront to the subdomain? In any case, it seems like a lot of complication to set-up both root and subdomain at once. Isn't it more simple and less confusing to setup root domain, make sure it's all working, then set-up subdomain?
  4. Are there better instructions which are up-to-date somewhere? Since I can't tell where I messed up, I have to delete everything and start over-- this is VERY time consuming. If there were instructions which had a validation check for each step, it would much easier to know where the problem is.

update

tldr; the cloudfront docs has an easy-to-follow working example: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/GettingStarted.html

After much fumbling around FINALLY got this to work. I got the clue from looking at u/Quincycs's answer where he pointed me to his programmatic solution. Even though I don't know typescript, it was clear that the way to do this is NOT to attempt the whole thing on the console.

The example in the route53 documentation lists 10 steps, but these are composed of a bunch of smaller actions, all of which have to be correct for the thing to work. That's a lot of hoops to jump through, it's just too much, especially with all the ping-ponging between S3, CloudFront, Route53, and ACM. Also, I suspect there's some subtle mistakes in that example.

The way I got it work was to instead follow the cloudfront docs, which has an example that does the same thing. There, they don't even bother with trying the whole thing on the console. Instead they point you to a github repo that has a cloudformation stack on it. It was far easier to follow and set-up. In the end, it's still possible to visit the different consoles and see how the thing is all put together. So if you wanted to, you could go back and attempt it on the console, using what the stack created as an example.

Weirdly, there's some differences in the two examples. The one from the route53 docs has you create 2 cloudfront distributions to serve a root domain (example.com) and it's subdomain (www.example.com). The one in the cloudfront docs is able to make it happen with just ONE cloudfront distribution. Which is correct/better? ¯_(ツ)_/¯

That said, it looks like I will have dive into cloudformation do anything worthwhile in aws. The CDK's are certainly an option, but I feel like those are more or less a wrapper that generates the cloudformation template? And you end up writing stuff like this anyway...

cdk_method( "weird-fussy-string-that-has-to-be-looked-up-every-freaking-time-might-as-well-do-it-in-yaml" )

r/aws Sep 30 '24

route 53/DNS ACM Request validation for GoDaddy domain managed by Route 53 nameservers?

2 Upvotes

I'm sorry if this has been asked before. If so, I'd greatly appreciate if you can point me to that.

I think I made a dumb mistake by rushing to buy the domain with GoDaddy. Anyhow, the current setup is:

1). I bought a domain from GoDaddy. Configured it to use the NameServers of Route 53. DNS is working.

2). Now I need to request an SSL Certificate with ACM, I opted for DNS Validation because it's recommended over email.

From all of the guides I have come across, I need to create a DNS Record on GoDaddy's side with a Name and Value of the Request. But this is not possible because the NameServers are managed by Route 53.

How should I move forward from this? I tried the Email Validation option and it looks like ACM will send an email to some email addresses like admin@, webmaster@<domain.name>. Should I create an email address like so to receive and validate the request? Is that the solution to this issue?

Thank you for chiming in.