#Route53

Version0.1 Version0.1 - やりたいところだけ実装するので永遠に完成しない。日々の作業ログや考えたことを残す技術ブログ。AWS中心の開発環境で、完成しないプロジェクトの記録と技術記事を公開

2 months ago

Well, there's absolutely no plan for impersonation accounts to appear at this point!

How to Set Up a Custom Domain ID on Bluesky
#Bluesky #Route53
v0-1.net/en/posts/blu...

0 0 0 0

Version0.1 Version0.1 - やりたいところだけ実装するので永遠に完成しない。日々の作業ログや考えたことを残す技術ブログ。AWS中心の開発環境で、完成しないプロジェクトの記録と技術記事を公開

2 months ago

まぁ今のところなりすましアカウントが発生する予定は全くないですけども！

BlueskyでカスタムドメインIDを設定する方法
#Bluesky #Route53
v0-1.net/ja/posts/blu...

0 0 0 0

Steef-Jan Wiggers

@steefjan.bsky.social

2 months ago

AWS Previews Route 53 Global Resolver to Decouple DNS from Regional Failures AWS previews Route 53 Global Resolver, using Anycast to decouple DNS from regional failures. It simplifies hybrid setups with unified public/private resolution, DoH/DoT, and Zero-Trust security.

AWS recently announced the public preview of Amazon Route 53 Global Resolver, a new service that provides secure, reliable DNS resolution globally. #anycast #amazonwebservices #dns #aws #route53 #amazon www.infoq.com/news/2026/01...

0 1 0 0

Version0.1 Version0.1 - やりたいところだけ実装するので永遠に完成しない。日々の作業ログや考えたことを残す技術ブログ。AWS中心の開発環境で、完成しないプロジェクトの記録と技術記事を公開

2 months ago

登録後の確認は力尽きたので明日書きます…。

Google Search Consoleに登録する方法 - Route 53を使った設定手順
#GoogleSearchConsole #SEO #Route53
v0-1.net/ja/posts/goo...

1 0 0 0

Version0.1 Version0.1 - やりたいところだけ実装するので永遠に完成しない。日々の作業ログや考えたことを残す技術ブログ。AWS中心の開発環境で、完成しないプロジェクトの記録と技術記事を公開

2 months ago

I'm too exhausted to confirm after registration, so I'll write about it tomorrow...

How to Register with Google Search Console - Setup Guide Using Route 53
#GoogleSearchConsole #SEO #Route53
v0-1.net/en/posts/goo...

1 0 0 0

Roman Naumenko

@naumenko.ca

3 months ago

Construct Hub Construct Hub helps developers find open-source construct libraries for use with AWS CDK, CDK8s, CDKTF and other construct-based tools.

Check this out: #CDK construct to manage route53 without zone delegation legacy
constructs.dev/packages/@ca...

Using it for all for all domains, subdomains, environments and multi-account app deployments. Deployed it and never had to touch #Route53 zones ever again.

0 0 0 0

Villpress

@villpress.com

3 months ago

AWS Unveils ‘Accelerated Recovery’ to Strengthen Route 53 DNS Reliability in US East-1 - Villpress Amazon Web Services (AWS) has launched Accelerated Recovery, a new DNS resiliency feature for Amazon Route 53 designed to boost reliability in the frequently

🚨 AWS launches Accelerated Recovery for Route 53!
A new feature promising 60-min DNS recovery during US East-1 outages.
Free. Opt-in. Replicates zones to US West-2.
A big win for uptime. 🔥

Continue reading below
villpress.com/aws-unveils-...

#AWS #Route53 #Cloud

1 0 0 0

Tatiana Mikhaleva

@devops.pink

3 months ago

Forget the Docs - Amazon Q Actually Teaches You AWS DNS YouTube video by DevOps Pink | by Docker Captain

Just dropped a new short 💖🔥

If Route 53 ever made you feel like it’s your first day in AWS… this one’s for you 😅

Q breaks down DNS like you’re a genius - not a confused intern.

Go watch👇
youtube.com/shorts/yCN-L...

#YouTubeShorts #AWS #Route53 #AmazonQ #DevOps #Cloud

1 0 0 0

Nicholas Dille

@nicholas.dille.name

4 months ago

Today I tried to revive an old pipeline with a #CloudFormation stack for #AWS #Route53. I was not aware that DNS records do not support drift detection. Manually modified record targets will not be corrected. Migrated the whole thing to #Terraform - works like a charm

1 0 0 0

Ryan Wetzelberger

@wetzellabs.com

4 months ago

DNS is the backbone of the internet, making it easy to reach websites. With Kubernetes, ExternalDNS auto-publishes DNS records to Route53, simplifying public access to apps. Learn more: https://bit.ly/4618MFa

1 0 0 0

@cryonautlex.bsky.social

5 months ago

No worries! I successfully acquired the domain and its most common misspelling on #AWS #Route53 before anyone else could.

3 0 0 0

AWS Community Builder Blog Posts

@awscmblogposts.bsky.social

6 months ago

The smart way of centralizing VPC endpoints with Route 53 Profiles How to Centralize Endpoints Smartly A few months ago in April, AWS introduced a new...

✍️ New blog post by Martin Nanchev

The smart way of centralizing VPC endpoints with Route 53 Profiles

#aws #dns #route53 #awscommunitybuilders

0 0 0 0

aster.cloud

@aster-cloud.bsky.social

7 months ago

Host a static website on AWS with Amazon S3 and Route 53 - aster.cloud Want to quickly and affordably get your website hosted in the cloud? If you don’t need advanced services such as EC2 or Fargate, a simple S3-hosted website might be the…

Host a static #website on #AWS with #AmazonS3 and #Route53

#WebDevelopment #Web

aster.cloud/2025/06/27/h...

1 0 0 0

@inmobi-info.bsky.social

8 months ago

【小ネタ】AWS Route53で購入できるドメインコストをまとめました（2025.07.05時点） #route53 – Qiita いつも記事を読んでいただきありがとうございます！モブエンジニア（@mob-engineer)です！新卒研修内でRoute53のドメインコストについて調べることがあったのですが、ドメインごとのコストについてまとまっている情報がないなと思いましたので簡単にまとめました。小ネタレベルの記事ですがお気軽にお読みいただけますと幸いです。（参考）Route 53でドメインを購入する方法ご存じの方も多くいらっしゃるかと思いますが簡単にまとめます。コンソール画面上部の検索ボックスにを入力検索結果よりをクリック Route53メニュー画面が表示されるため、左側ペインの[登録済みドメイン]をクリック AWS上で管理しているドメイン一覧画面が表示されるため、画面上部の[ドメインを登録]をクリックドメイン一覧が表示されます任意の名前を入力し検索すると、作成可能なドメイン名が表示されます [選択済み]をクリックし、[チェックアウトに進む]ボタンをクリックします [自動更新のオン/オフ]を指定できるため要件に応じて変更します [次へ]ボタンをクリックします [連絡先情報]が表示されます任意の情報・プライバシー保護設定を行い、[次へ]ボタンをクリックしますデフォルトでプライバシー保護が有効化されているのはうれしいですね。利用規約にチェックボックスを入れ、[送信]ボタンをクリックすることでRoute53で管理できるドメインを作成できます。組織改編等で登録情報を変更する場合もRoute53から変更可能ですドメインコストここから本編のドメインコストをまとめていきたいと思います。分かりやすいように、年間費用が安い順にランク付けして表形式でまとめたいと思います。

【小ネタ】AWS Route53で購入できるドメインコストをまとめました（2025.07.05時点） #route53 – Qiita

いつも記事を読んでいただきありがとうございます！モブエンジニア（@mob-engineer)です！新卒研修内でRoute53のドメインコストについて調べることがあったのですが、ドメインごとのコストについてまとまっている情報がないなと思いましたので簡単にまとめました。小ネタレベルの記事ですがお気軽にお読みいただけますと幸いです。（参考）Route 53でドメインを購入する方法ご存じの方も多くいらっしゃるかと思いますが簡単にまとめます。…

0 0 0 0

aster.cloud

@aster-cloud.bsky.social

8 months ago

Host a static website on AWS with Amazon S3 and Route 53 - aster.cloud Want to quickly and affordably get your website hosted in the cloud? If you don’t need advanced services such as EC2 or Fargate, a simple S3-hosted website might be the…

Host a static #website on #AWS with #AmazonS3 and #Route53

#WebDevelopment #Web

aster.cloud/2025/06/27/h...

2 0 0 0

@inmobi-info.bsky.social

9 months ago

AWS Transfer Family で SFTP サーバーを構築して閉域のオンプレミスからエンドポイント経由で S3 にアクセスする #route53 システム間で認証認可が必要なファイル連携をすることを考える時、例えば連携したいシステムがいずれも AWS に構築しているのであれば、Amazon S3 を使うのが効率的です。ここで、地方公共団体情報システムの標準化における標準準拠システム間でファイル連携をする場合は、オブジェクトストレージを使った連携を行う仕様となっており、閉域の環境からオブジェクトストレージにアクセスした上で、通信を暗号化し、認証認可も必要なことから、AWS 環境同士の連携であれば S3 を使った連携を構築することが多いです。一方、AWS と他の CSP 環境、オンプレミスとの連携をする場合でかついずれも閉域である場合、AWS のマネージドサービスだけでは認証認可が行えないため、個別に認証認可サーバーを立てるなどの対応が必要です。認証認可サーバーの管理は手間がかかるため、なるべく AWS のマネージドサービスに寄せつつ、オブジェクトストレージを使った、暗号化通信が可能で、認証認可も行えるサービスを考えた時、AWS Transfer Family で SFTP サーバーを構築することが候補となります。 AWS Transfer Family であれば、認証に関するユーザー管理を AWS 側で行うことができ、かつ IAM ロール、IAM ポリシーでバケットに対するアクセス権限を管理することができます。そこで、ガバメントクラウド環境で使うことを想定し、閉域のオンプレミスと AWS を接続し、オンプレミスのクライアントから Transfer Family の VPC エンドポイント経由で、SFTP で S3 バケットにファイルを連携する構成について試してみました。構築する Transfer Family 検証環境の概要内部向けの VPC エンドポイントしか持たない Transfer Family の SFTP サーバーを立てます。 VPN で VPC に接続している閉域のオンプレミス環境の SFTP クライアントから、Transfer Family の VPC エンドポイント経由でアクセスします。

AWS Transfer Family で SFTP サーバーを構築して閉域のオンプレミスからエンドポイント経由で S3 にアクセスする #route53

システム間で認証認可が必要なファイル連携をすることを考える時、例えば連携したいシステムがいずれも AWS に構築しているのであれば、Amazon S3 を使うのが効率的です。ここで、地方公共団体情報システムの標準化における標準準拠システム間でファイル連携をする場合は、オブジェクトストレージを使った連携を行う仕様となっており、閉域の環境からオブジェクトストレージにアクセスした上で、通信を暗号化し、認証認可も必要なことから、AWS…

0 0 0 0

AWS Route 53 Explained: Everything About Domains, DNS, and Hosted Zones Discover how AWS Route 53 handles domain names and DNS management.

9 months ago

"AWS Route 53 Explained: Everything About Domains, DNS, and Hosted Zones" by Jay Tillu

#aws #route53 #awsroute53 #amazonwebservices #dns

0 0 0 0

Route 53 Resolver: Streamlining DNS with Profiles (Part 3) Part 3 dives into Route 53 Profiles, showing how to streamline DNS across VPCs and manage DNS for PrivateLink endpoints with ease.

9 months ago

"Route 53 Resolver: Streamlining DNS with Profiles (Part 3)" by Anjali Vijayakumar

#route53 #dns #hybridcloud #networking #vpc

0 0 0 0

Route 53 Resolver: AD Integration & Multi-VPC DNS (Part 2) Part 2 explores Active Directory integration and managing DNS in a multi-VPC environment

9 months ago

"Route 53 Resolver: AD Integration & Multi-VPC DNS (Part 2)" by Anjali Vijayakumar

#route53 #dns #networking #hybridcloud #vpc

0 0 0 0

Route 53 Resolver: DNS in Hybrid Cloud (Part 1) Dive into Amazon Route 53 Resolver in Part 1. Learn how it simplifies hybrid cloud DNS with managed endpoints for fast and reliable DNS resolution.

9 months ago

"Route 53 Resolver: DNS in Hybrid Cloud (Part 1)" by Anjali Vijayakumar

#route53 #dns #hybridcloud #vpc #networking

0 0 0 0

Let's Encrypt DNS01 Challenge with Traefik and AWS Route 53 Learn how to use Let's Encrypt, Traefik, and AWS Route 53 to get HTTPS certificates via DNS challenge; ideal when port 80 is blocked.

10 months ago

"Let's Encrypt DNS01 Challenge with Traefik and AWS Route 53" by Kasun de Silva

#route53 #traefik #dns #letsencrypt #awscommunitybuilders

0 0 0 0

AWS Community Builder Blog Posts

@awscmblogposts.bsky.social

10 months ago

Let's Encrypt DNS Challenge with Traefik and AWS Route 53 So, you're self-hosting awesome apps like Jellyfin, Home Assistant, or your personal blog with...

✍️ New blog post by Kasun de Silva

Let's Encrypt DNS Challenge with Traefik and AWS Route 53

#route53 #letsencrypt #dns #traefik

0 0 0 0

AWS Community Builder Blog Posts

@awscmblogposts.bsky.social

10 months ago

From Plex to Freedom: My Jellyfin Journey with Traefik & AWS Route 53 Like many, I relied on Plex for years to manage and stream my personal media library – hundreds of...

✍️ New blog post by Kasun de Silva

From Plex to Freedom: My Jellyfin Journey with Traefik & AWS Route 53

#route53 #dns #traefik #jellyfin

0 0 0 0

DEV Community

@dev.to.web.brid.gy

10 months ago

[AWS][Update]Amazon Route 53 Profiles now supports VPC endpoints #### Notice The AWS console screen is in Japanese. # introduction Thank you for always reading my articles! On Tuesday, April 29, 2025, we received some interesting update information about Route 53, so we would like to write an article summarizing the pros and cons of using it. The article is written in simple language so that even those who don't know anything about networks can understand, so I hope you will feel free to read it. # Update Information The contents of the official AWS blog are as follows: https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-route-53-profiles-vpc-endpoints/ > Today, AWS announced support for VPC endpoints in Amazon Route 53 Profiles, allowing you to create, manage, and share private hosted zones (PHZs) for interface VPC endpoints across multiple VPCs and AWS accounts within your organization. With this enhancement, Amazon Route 53 Profiles simplifies the management of VPC endpoints by streamlining the process of creating and associating interface VPC endpoint managed PHZs with VPCs and AWS accounts, and without requiring you to manually associate them. > Route 53 Profiles makes it easy for you to create one or more configurations for VPC-related DNS settings, such as private hosted zones and Route 53 Resolver rules, and share them across VPCs and AWS accounts. The new capability helps you centralize the management of PHZs associated with interface VPC endpoints, reducing administrative overhead and minimizing the risk of configuration errors. This feature eliminates the need for creation and manual association of PHZs for VPC endpoints with individual VPCs and accounts, saving time and effort for network administrators. Additionally, it improves security and consistency by providing a centralized approach to managing DNS resolution for VPC endpoints across an organization's AWS infrastructure. To put it very simply, you can think of Amazon Route 53 profiles as also managing VPC endpoints.Personally, I think this is a welcome update as it allows you to configure private hosted zones entirely through profile settings, which will help reduce operational costs. ### Using Regions The regions where this function is available are those where private hosted zones are available. According to the documentation, it is available in the following regions: https://docs.aws.amazon.com/general/latest/gr/r53.html * US East (Ohio) us-east-2 * US East (N. Virginia) us-east-1 * US West (N. California) us-west-1 * US West (Oregon) us-west-2 * Africa (Cape Town) af-south-1 * Asia Pacific (Hong Kong) ap-east-1 * Asia Pacific (Hyderabad) ap-south-2 * Asia Pacific (Jakarta) ap-southeast-3 * Asia Pacific (Melbourne) ap-southeast-4 * Asia Pacific (Mumbai) ap-south-1 * Asia Pacific (Osaka) ap-northeast-3 * Asia Pacific (Seoul) ap-northeast-2 * Asia Pacific (Singapore) ap-southeast-1 * Asia Pacific (Sydney) ap-southeast-2 * Asia Pacific (Tokyo) ap-northeast-1 * Canada (Central) ca-central-1 * Canada West (Calgary) ca-west-1 * Europe (Frankfurt) eu-central-1 * Europe (Ireland) eu-west-1 * Europe (London) eu-west-2 * Europe (Milan) eu-south-1 * Europe (Paris) eu-west-3 * Europe (Spain) eu-south-2 * Europe (Stockholm) eu-north-1 * Europe (Zurich) eu-central-2 * Israel (Tel Aviv) il-central-1 * Middle East (Bahrain) me-south-1 * Middle East (UAE) me-central-1 * South America (São Paulo) sa-east-1 * AWS GovCloud (US-East) us-gov-east-1 * AWS GovCloud (US-West) us-gov-west-1 It is not available in the recently released Thailand region, but it is available in the Tokyo and Osaka regions, so it should not be a problem for businesses operating domestically. #### Notice There will be no change in usage fees compared to the regular Route 53 Profile. ## Checking Updates #### Notice Detailed configuration instructions are summarized in the following official document: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/profile-associate-vpc-endpoints.html I created one endpoint for easy verification. #### Warning This could not be set with the VPC endpoint that is created by default when creating a VPC. You can associate the endpoint by creating it with com.amazonaws.ap-northeast-1.profile as the service name. * Endpoint Name:Route53-Profile-Test Now, let’s link the VPC we created to the Route 53 Profile. * Click on Profiles in the left pane of the Route 53 menu. * The profile menu screen will appear, so click the Create Profile button. * The profile creation screen will appear, so enter any value for the profile name and click the Create Profile button. * I was able to create a profile * Click on the VPC Endpoints tab and click on the Associate button. * A list of VPC endpoints will be displayed. Click the check box to the left of the endpoint that says "Ready to associate". * After clicking, click the Create Profile button. * The association process itself seems to be working fine, but the VPC endpoint association count has not changed. **We plan to test Route 53 in the future, so we will test it at that time.** ## Benefits of using it in practice Although the test itself did not go as expected, I would like to briefly summarize the benefits of using it that I felt after actually using it. #### Merit * Easier association of profiles and endpoints. * You can check the associated endpoint information just by looking at the profile. * Network management becomes easier, reducing the burden on network operators. Having said that, I noticed that there are a few things to keep in mind when using it, so I have summarized those as well. #### Caution * Each profile can have up to 10 endpoints associated with it. * It is unclear whether one endpoint can be linked to multiple endpoints. * The linking itself is easy, but in an environment with multiple profiles, there is a possibility of misconfiguration. ## Conclusion Although it is a simple update, it is an interesting one for future network operations, so I will continue to watch it. Thank you for reading the article to the end!

0 0 0 0

Raptus

@rgp.io

11 months ago

@xpaw.me encountered similar issue when browsing crowdin.com which also appears to use #AWS #Route53

0 0 0 0

Raptus

@rgp.io

11 months ago

Output from DNS lookup with nslookup: Name: use22-0.playlist.ttvnw.net Addresses: 3.131.34.179 18.224.80.62 3.16.115.115 3.142.179.252 3.130.184.162 3.18.26.231 3.146.239.104 3.21.192.195

Output from checking the webserver certificate for each IP from the DNS response: 3.131.34.179* subject: CN=caplearn.icfcloud.com 18.224.80.62* subject: CN=use22-0.playlist.live-video.net 3.16.115.115 timeout 3.142.179.252 timeout 3.130.184.162* subject: CN=use22-0.playlist.live-video.net 3.18.26.231* subject: CN=ecomm.ui.com 3.146.239.104* subject: CN=use22-0.playlist.live-video.net 3.21.192.195 timeout

Screenshot of the Chrome addressbar show "Not secure" error due to wrong certificate

Something dodgy going on with #AWS #Route53 where DNS servers respond with incorrect A records for a #twitch domain. This manifest as certifcate errors in Chrome. Below is an example of the issue where only 3 out of 8 A records are correct. 🤔

0 0 1 0

Abhishek Dey Das

@abhishek.deydas.me

11 months ago

I was trying to create a new #aws #cloudfront distribution and got this error on my #cloudformation stack. For me, it was a several year old distribution with the same CNAME, although the distribution was not in use. The error could also be from #route53 records in the same or different regions.

0 0 0 0