brandon/oam
1
0
Fork 0
mirror of https://gitea.com/mcereda/oam.git synced 2026-02-09 05:44:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
14e8aa195d4e0fe5df2501fafb4f7a06a6db721b
oam/knowledge base/cloud computing/aws/route53.md
Michele Cereda 2ffd380228 chore(aws/route53): expand split-view notes
2024-11-15 21:41:51 +01:00

2.7 KiB
Raw Blame History

Route 53

AWS DNS service offering.

  1. TL;DR
  2. Split-view
  3. Further readings
    1. Sources

TL;DR

Usage 
# List hosted zones.
aws route53 list-hosted-zones

Split-view

A.K.A split-horizon DNS.

Allows to use the same domain name for both internal and external uses.

Procedure:

  1. Enable DNS resolution and DNS hostnames for any VPC involved.

  2. Create public and private hosted zones with the same name.
    Split-view DNS will still work if using an external DNS service for the public hosted zone.

  3. Associate one or more VPCs with the private hosted zone.
    Route 53 Resolver will use the private hosted zone to route DNS queries in the associated VPCs.

  4. Create records in each hosted zone.

    Records in the public hosted zone will control how internet traffic is routed.
    Records in the private hosted zone will control how traffic is routed inside the associated VPCs.

  5. Use Route 53 Resolver to perform name resolution of both the associated VPC and on-premises workloads.

DNS queries for public DNS record from VPCs attached to private hosted zone will not resolve and will give back NXDOMAIN errors.
If a record doesn't exist in the private hosted zone, the DNS query cannot be forwarded to a public hosted zone.

Resolve public DNS records from VPCs associated with private hosted zones by replicating all public records in the private hosted zone along with private records.
Any query coming from a public DNS record will be resolved from the private hosted zone.

Further readings

Sources