Domain name system
The Domain Name System is a distributed, hierarchical naming system that resolves domain names to IP addresses and other network resource records.
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
The Domain Name System is a distributed naming system that translates domain names into network addresses and related resource records.
- How it is used
- Resolves application-facing domain names into addresses and supports Cisco IOS client, server, configuration, and troubleshooting tasks.
- How deep it goes
- Explains URLs, caching, transport, hierarchy, records, and IOS commands with verification, while stopping short of detailed recursive-resolution internals.
- Examples
- Uses www.google.com resolution, URL parsing, cache inspection, DNS record tables, Cisco ping output, and local IOS host mappings.
- What you can do after
- Operate/configure Cisco IOS DNS clients and servers, verify resolution, and diagnose missing or manually mapped hostnames.
Acing the Certified Kubernetes Administrator Exam, Second Edition
The Domain Name System, a hierarchical naming system that resolves domain or resource names to network addresses.
- How it is used
- Uses DNS for pod and Service discovery by name within a Kubernetes cluster.
- How deep it goes
- Works through namespace lookup, CoreDNS availability, replica scaling and a DNS Service IP change; does not explain DNS protocol internals.
- Examples
- Tests cross-namespace Service names with curl, inspects /etc/resolv.conf and verifies resolution with nslookup.
- What you can do after
- Operate/configure it with kubectl and kubelet settings, then verify a new pod’s DNS server and name resolution.
Build Python Web Apps with Streamlit
DNS is the naming system that maps human-readable domain names and subdomains to network resources.
- How it is used
- Connects a registered domain or subdomain to a deployed Elastic Beanstalk application.
- How deep it goes
- Explains DNS through a phone-book analogy and a CNAME setup, stopping short of broader record types or resolution internals.
- Examples
- Uses www.factfrenzyapp.com and fact-frenzy.us-east-2.elasticbeanstalk.com as a custom-domain mapping example.
- What you can do after
- Operate a DNS dashboard to register a domain and configure a CNAME for an Elastic Beanstalk application.
Read how Build Python Web Apps with Streamlit explains domain name system →
ASP.NET Core in Action, 3e
DNS is the hierarchical naming system that resolves hostnames to IP addresses and other network records.
- How it is used
- Connects browser navigation and outbound HTTP calls to the server’s IP address.
- How deep it goes
- Defines hostname-to-IP mapping and lookup timing, but stops short of DNS record types or resolver internals.
- Examples
- Uses microsoft.com, www.google.co.uk, facebook.com, and HttpClient connections as concrete hostname examples.
- What you can do after
- Evaluate how hostname resolution precedes HTTP connections and why changing DNS can affect long-lived HttpClient instances.
Read how ASP.NET Core in Action, 3e explains domain name system →
Rust in Action: Systems programming concepts and techniques
The Domain Name System is a distributed naming system that maps domain names to network resource records such as IP addresses.
- How it is used
- Uses distributed name resolution to obtain IP addresses before sending internet messages.
- How deep it goes
- Explains recursive resolution and constructs an IPv4 query, but delegates most protocol details to trust-dns.
- Examples
- Demonstrates the resolve command, public DNS services, and a Rust message requesting an IPv4 A record.
- What you can do after
- Build it from scratch: create a command-line Rust utility that resolves hostnames through a selected DNS server.
Read how Rust in Action: Systems programming concepts and techniques explains domain name system →
Learn Docker in a Month of Lunches, Second Edition
DNS is the Domain Name System, a distributed naming system that resolves domain names to network addresses.
- How it is used
- Uses DNS for Docker container service discovery when changing container addresses would make direct addressing unreliable.
- How deep it goes
- Explains name resolution, Docker forwarding, and scaled lookup results, but stops short of DNS protocol internals.
- Examples
- Demonstrates nslookup from a web container against accesslog and scaled iotd services.
- What you can do after
- Diagnose container connectivity by scaling Compose services and inspecting Docker DNS results with nslookup.
Read how Learn Docker in a Month of Lunches, Second Edition explains domain name system →
Grokking Web Application Security
The Domain Name System (DNS) is the hierarchical naming system that maps domain names to network addresses and other DNS records.
- How it is used
- Explains how browsers resolve domain names into IP addresses before connecting to internet services.
- How deep it goes
- Traces root, top-level-domain, and authoritative lookups plus caching, but stops short of detailed poisoning mechanics.
- Examples
- Uses https://www.example.com and browser, operating-system, ISP, and corporate-network caches as concrete lookup examples.
- What you can do after
- Understand how hierarchical DNS resolution and caching support web requests and create opportunities for traffic diversion.
Read how Grokking Web Application Security explains domain name system →
Related concepts
- UDPuses · UDP (User Datagram Protocol) is a connectionless transport-layer protocol that sends datagrams without guaranteeing delivery, ordering, or duplicate suppression.
- TCPuses · TCP is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of byte streams between network endpoints.
- IP addressproduces · An IP address is a numerical address used by the Internet Protocol to identify a network interface and support packet delivery across networks.
- nslookupused by · nslookup is a command-line utility that queries Domain Name System servers and displays domain names, addresses, and other resource records.
- service discoveryused by · Service discovery is the process of identifying available services and obtaining the names, locations, or connection information needed to access them.
- CoreDNSused by · CoreDNS is an extensible, plugin-based DNS server commonly used in Kubernetes clusters for service and workload name resolution.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.