# DNS

DNS (Domain Name System) is a distributed, hierarchical naming system that translates domain names into IP addresses and other resource information.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/dns

> DNS lets applications and users find resources through stable names instead of hard-coded network addresses. In the cloud, it supports public websites, private service discovery, and endpoint selection while allowing the underlying infrastructure to change.

Practice exams covering DNS: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of DNS

DNS combines delegated naming, typed records, caching, and scoped visibility to provide stable resource discovery and indirect endpoint selection.

1. **Hierarchical naming and delegation**: DNS distributes responsibility across a hierarchy of zones and authoritative name servers. Correct delegation is essential: creating records at a DNS provider does not make them effective unless queries are directed to that provider's authoritative servers.
2. **Typed resource records**: Different record types represent addresses, aliases, mail routing, and other information. Choose records according to the endpoint and protocol rather than assuming every name maps directly to a single IP address.
3. **Recursive resolution and caching**: Recursive resolvers obtain answers for clients and cache them according to TTLs. Account for cached answers when planning migrations, investigating inconsistent results, or estimating failover time.
4. **Public and private namespaces**: Public DNS supports internet-facing names, while private DNS makes names available within configured network scopes. DNS visibility and network access are separate controls, so successful resolution does not prove that a connection is permitted.
5. **DNS-based endpoint selection**: DNS policies can return different endpoints based on weights, location, latency estimates, or health. This steers future connections indirectly and does not provide per-request load balancing or immediate failover.
6. **Naming security and administrative control**: Secure domain registration, delegation, and record-management permissions to prevent unauthorized redirection. DNSSEC supports authenticity and integrity of DNS data, while encrypted DNS transport and HTTPS address different security needs.

## Cloud services for DNS

Amazon Route 53 publishes DNS records that connect application names to cloud entry points. For a regional application, a Route 53 alias record can target an Elastic Load Balancing endpoint, after which the load balancer distributes connections or requests to healthy targets. For an application using edge delivery, the name can target a CloudFront distribution, which serves cached content or forwards requests to its configured origin. These responsibilities remain distinct: DNS supplies endpoint information, CloudFront handles edge delivery, and load balancers distribute traffic. DNS caching affects how quickly clients observe changes to those entry points.

- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Provides authoritative DNS through public and private hosted zones, domain registration for supported top-level domains, and health checks. Routing policies can select DNS answers using criteria such as weights, latency, and endpoint health.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: Uses DNS as part of directing viewers to its content delivery infrastructure. A custom domain can point to a distribution, but the distribution must also be configured for that hostname and, for HTTPS, have an appropriate certificate.

## DNS exam questions

Real practice exam questions on DNS, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company has registered a domain name with a third-party provider and hosts its public website in an on-premises data center. The company wants AWS to manage the public DNS records that direct visitors to the website, without transferring the domain registration or moving the website. Which solution meets these requirements?

**Correct answer:** Create an Amazon Route 53 public hosted zone, add the website's DNS records, and update the domain's name server delegation at the registrar.

**Explanation:** A Route 53 public hosted zone manages publicly resolvable DNS records, including records pointing to infrastructure outside AWS. Updating the name server delegation lets Route 53 provide DNS hosting while the registration and website remain with their existing providers.

### Question 2 (SOA-C03)

**Question:**

A company hosts example.com in an Amazon Route 53 public hosted zone and maintains the domain registration with a third-party registrar. A CloudOps engineer enables DNSSEC signing for the hosted zone. The key-signing key is active, and the authoritative name servers return DNSKEY and RRSIG records. However, an independent DNSSEC test reports that no chain of trust exists from the .com zone to example.com. Normal DNS resolution still succeeds, and the registrar configuration has not been updated since signing was enabled.

Which action should the engineer take to establish the chain of trust?

**Correct answer:** Submit the DS record details for the active Route 53 key-signing key to the registrar so that the registrar publishes the DS record in the .com zone.

**Explanation:** The parent zone's DS record identifies the child's trusted signing key. Providing Route 53's DS record details through the registrar establishes the chain of trust from .com to the signed example.com zone.

### Question 3 (ANS-C01)

**Question:**

A company runs a high-volume TCP service behind one internal Network Load Balancer (NLB) enabled in three Availability Zones. Each zone contains service targets and client instances. The target group inherits the NLB's cross-zone load balancing setting. All zones have sufficient capacity to handle a zone failure.

The client software supports a preferred endpoint and a fallback endpoint. Each client is configured with a preferred hostname corresponding to its own Availability Zone and a shared fallback hostname. If connections to the preferred endpoint fail, the client resolves the fallback hostname and retries. Clients periodically refresh DNS results.

The company wants connections to remain entirely within the client's Availability Zone during normal operation to minimize latency and cross-AZ transfer charges. If that zone's service targets become unavailable, clients must be able to reconnect through healthy zones after health checks and DNS changes converge. The company must retain the single NLB and must not maintain load balancer IP addresses in DNS manually.

Which configuration meets these requirements?

**Correct answer:** Create a Route 53 private hosted zone associated with the client VPC. Create each preferred hostname as a CNAME to the NLB's corresponding zonal DNS name, and create the fallback hostname as an A alias to the NLB's regional DNS name. Disable cross-zone load balancing on the NLB.

**Explanation:** Each preferred CNAME selects the NLB node in the client's Availability Zone. With cross-zone load balancing disabled and the target group inheriting that setting, the node forwards connections only to targets in that zone. The regional fallback name lets the client's retry mechanism reach other healthy zones. NLB DNS health behavior removes an unhealthy zone from regional DNS responses after health detection, assuming other zones remain healthy. Both record types follow AWS-managed DNS without manually maintaining IP addresses.

### Question 4 (SAA-C03)

**Question:**

A company hosts a public application on servers with fixed public IPv4 addresses. A non-alias A record in an Amazon Route 53 public hosted zone points to the current servers and has a TTL of 86,400 seconds. The company will migrate the application to new servers in 48 hours.

The old servers must be decommissioned 10 minutes after the DNS address change to avoid paying for another day of hosting. All DNS resolvers used by the application's clients honor record TTLs and do not serve expired answers. Clients perform a new DNS lookup for each new connection, and existing connections are outside the scope of the migration.

Which approach will prevent new connections from using the old addresses after the decommissioning deadline while minimizing ongoing authoritative DNS query charges outside the migration period?

**Correct answer:** Set the A record's TTL to 300 seconds now. At the scheduled migration, change the record to the new addresses. Restore the original TTL after the 10-minute transition period.

**Explanation:** The 48-hour lead time lets all answers cached with the original 24-hour TTL expire before migration. At the address change, cached old answers have no more than 300 seconds remaining, so they expire before the 10-minute deadline. Restoring the longer TTL afterward improves cache reuse and reduces ongoing authoritative DNS queries.

## Practice DNS in a full exam

Questions on DNS in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 18 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 10 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 8 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 5 questions

## What is DNS

DNS separates a resource's name from its network location. When a user opens https://www.example.com, the client typically asks a recursive DNS resolver for the address associated with www.example.com. The resolver returns a cached answer or follows the DNS hierarchy through root, top-level domain, and authoritative name servers. The client then connects to the returned address. DNS resolves the hostname, not the entire URL: it does not interpret the HTTPS scheme, path, or query string.

Authoritative DNS servers publish records for zones, which are administratively managed portions of the DNS namespace. A records contain IPv4 addresses, AAAA records contain IPv6 addresses, and CNAME records point one name to another name. MX records identify mail servers, while TXT records hold text commonly used for domain verification and email authentication. NS records identify authoritative name servers and support delegation. Registering a domain, hosting its DNS records, and hosting its website are separate functions that can use different providers.

Cloud environments use DNS to keep names stable while infrastructure changes. For example, app.example.com can point to a managed load balancer rather than directly to a virtual machine. The load balancer can distribute requests across instances that are replaced or scaled independently. Provider-specific alias records can map a custom name to supported cloud resources; these are not the same as standard CNAME records. A standard CNAME cannot normally coexist with other records at the same name, which prevents its use at a zone apex where required records already exist.

Public DNS publishes information intended to be resolvable through the public DNS hierarchy. Private DNS serves names within designated networks, such as application and database names inside a virtual private cloud. Hybrid environments can forward selected queries between cloud networks and on-premises resolvers. Resolving a private name does not itself provide connectivity: routing, firewall rules, and application permissions must still allow access.

Caching makes DNS efficient and resilient, but it complicates changes. A record's time to live, or TTL, tells caches how long they may retain an answer before refreshing it. Longer TTLs reduce query traffic and dependence on authoritative servers; shorter TTLs allow cached answers to expire sooner but can increase query volume and cost. Before a planned endpoint migration, lower the TTL early enough for previously cached answers to expire. Changing a record does not instantly update every client, and existing connections can continue using the old destination.

DNS can also influence endpoint selection through weighted, latency-based, geographic, or health-aware responses. These policies select DNS answers rather than forwarding application traffic. DNS-based failover is therefore not instantaneous, and weighted answers do not guarantee an exact percentage of application requests because resolvers cache responses and many users can share a resolver.

For AWS Cloud Practitioner questions, recognize Amazon Route 53 as the AWS service for authoritative DNS, domain registration for supported top-level domains, and health checks that can inform DNS failover. It is not a web server, content delivery network, or application load balancer. For example, Route 53 can resolve a custom domain to a CloudFront distribution or an Elastic Load Balancing endpoint, while those services handle the subsequent application traffic.

DNS is also a security dependency. Protect registrar and DNS administration access because unauthorized record changes can redirect users. DNSSEC can authenticate signed DNS data when validation is performed, but it does not encrypt DNS queries or replace HTTPS. When troubleshooting, check delegation, record type, cached answers, resolver behavior, and network reachability as separate concerns.

## Learn DNS in lessons

3 short lessons on DNS in 3 certification courses.

- CLF-C02: DNS: resolving names to resource endpoints (Premium), https://app.blowstack.com/lessons/dns-resolving-names-to-resource-endpoints-clf-c02
- SOA-C03: DNS: resolver paths and conditional forwarding (Premium), https://app.blowstack.com/lessons/dns-resolver-paths-and-conditional-forwarding-soa-c03
- SAA-C03: DNS: name resolution for cloud endpoints (Premium), https://app.blowstack.com/lessons/dns-name-resolution-for-cloud-endpoints-saa-c03
