32 of 50 in All Controls
aws

Centralize DNS Management with Route 53

IDAWS-NET-004
Severity
medium
Automation
Auto
Category
network
Enforcementrecommended
Complexity / Impact
medium(low impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:ou
Environments
productionnon-productionsandbox
Target Resources
AWS::Route53::HostedZoneAWS::Route53Resolver::ResolverEndpointAWS::Route53Resolver::ResolverRuleAWS::Route53Resolver::FirewallRuleGroup
Services
route-53route53resolverramec2
Tags
networkdnsroute53centralizationlanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (annually)
Created
2026-05-03
Last Updated
2026-11-16

Specification & Description

Establish centralized DNS management using Route 53 Resolver and private hosted zones in the Network account, with cross-account VPC association authorization and query logging.

Technical Specifications

Scattering internal DNS hosted zones across individual accounts leads to fragmented name resolution, overlapping record namespaces, and unmonitored DNS exfiltration paths. Centralizing Route 53 Private Hosted Zones (PHZs) in the Network account enables controlled record management and shared resolution for internal corporate domains. Member account VPCs link to central hosted zones using cross-account association authorizations. Route 53 Resolver endpoints provide conditional forwarding to on-premises DNS, and Route 53 Resolver query logging captures all DNS traffic across VPCs for security monitoring.

Security Rationale

Centralized DNS management provides consistent domain name resolution, prevents split-brain namespace conflicts, and establishes a control plane for DNS security. Centralizing Route 53 Resolver rules and private zones ensures organizations enforce DNS firewall blocklists and capture forensic query logs across all accounts.

Business & Security Impact

Fragmented DNS resolution creates service connectivity failures, exposed internal records, and blind spots during security incidents. Unmonitored DNS queries prevent teams from detecting DNS tunneling, beaconing, and malware domain communications.

Compliance Framework Mappings (4)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
NIST 800-53 Rev 5NIST 800-53
SC-20SC-21AU-12
3
ISO 27001:2022ISO 27001
A.8.20A.8.21
2
PCI DSS v4.0PCI DSS
1.2.1
1
SOC 2SOC 2
CC6.6
1

* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.

Automated Detection & Rule Logic

Detection Engine: aws-api • Automated: Yes

Audit Route 53 to confirm that internal private hosted zones are active and properly associated with VPCs, and verify that Route 53 Resolver query log configurations exist and attach to landing zone VPCs.

Audit Private Hosted Zones and Resolver Query Log Associationsbash
# 1. Audit Private Hosted Zones in the account
aws route53 list-hosted-zones \
  --query "HostedZones[?Config.PrivateZone==\`true\`].{Id:Id,Name:Name,RecordCount:ResourceRecordSetCount}" \
  --output json

# 2. Verify Route 53 Resolver endpoints operational status
aws route53resolver list-resolver-endpoints \
  --query "ResolverEndpoints[?Status=='OPERATIONAL'].{Id:Id,Name:Name,Direction:Direction,IpCount:IpAddressCount}" \
  --output json

# 3. Audit Resolver query log configurations and active VPC associations
aws route53resolver list-resolver-query-log-config-associations \
  --query "ResolverQueryLogConfigAssociations[?Status=='ACTIVE'].{AssociationId:Id,QueryLogConfigId:ResolverQueryLogConfigId,VpcId:ResourceId}" \
  --output json

Remediation Guide & Automation

In the Network account, create Route 53 Private Hosted Zones for internal domains and authorize member VPC associations. Configure Route 53 Resolver inbound and outbound endpoints for hybrid connectivity, deploy DNS Firewall domain blocklists, and enable Route 53 Resolver query logging across all landing zone VPCs.

Step-by-Step Instructions

  1. Create Private Hosted Zones (PHZs) in the Network account for internal domain namespaces.
  2. Authorize cross-account VPC associations from the Network account using create-vpc-association-authorization.
  3. Associate member account VPCs with the central PHZ.
  4. Deploy Route 53 Resolver endpoints across multiple Availability Zones for hybrid DNS resolution.
  5. Associate Route 53 Resolver query log configs with VPCs to capture DNS telemetry to CloudWatch Logs or S3.
Create Central PHZ, Authorize Cross-Account VPC, and Configure Query Loggingbash
# 1. Create Private Hosted Zone in Network Account
zone_id=$(aws route53 create-hosted-zone \
  --name "corp.internal" \
  --caller-reference "phz-corp-internal-$(date +%s)" \
  --vpc VPCRegion=us-east-1,VPCId=vpc-0123456789abcdef0 \
  --hosted-zone-config Comment="Central Landing Zone PHZ",PrivateZone=true \
  --query 'HostedZone.Id' \
  --output text)

# 2. Authorize member account VPC to associate with the central PHZ (run in Network account)
aws route53 create-vpc-association-authorization \
  --hosted-zone-id "$zone_id" \
  --vpc VPCRegion=us-east-1,VPCId=vpc-0spoke11111111111

# 3. Associate member account VPC with the hosted zone (run in Member account context)
aws route53 associate-vpc-with-hosted-zone \
  --hosted-zone-id "$zone_id" \
  --vpc VPCRegion=us-east-1,VPCId=vpc-0spoke11111111111

# 4. Create Route 53 Resolver query logging configuration
query_log_id=$(aws route53resolver create-resolver-query-log-config \
  --name "Central-DNS-Query-Logs" \
  --destination-arn "arn:aws:logs:us-east-1:123456789012:log-group:/aws/route53/queries" \
  --query 'ResolverQueryLogConfig.Id' \
  --output text)

# 5. Associate query log configuration with VPC
aws route53resolver associate-resolver-query-log-config \
  --resolver-query-log-config-id "$query_log_id" \
  --resource-id "vpc-0123456789abcdef0"

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.