Domain Name System (DNS)
IP addresses are used to identify devices on TCP/IP networks. Each computer in a network is assigned a name, which is generally easier to remember than its IP address. DNS is a protocol that translates fully qualified domain names (FQDNs) into IP addresses. DNS servers maintain directories that map domain names to their corresponding IP addresses. This allows the network to resolve both names to IP addresses and IP addresses to names. As a result, instead of connecting directly to an IP address, a client can send a resolution request to a DNS server.
When a client submits a domain name to a DNS server for resolution, the server will either resolve the name to an IP address using its local cache or contact another DNS server to obtain the IP address on behalf of the client.
Why use DNS?
DNS is a fundamental component of modern IP networking. Without DNS, SSL certificates cannot be validated against domain names, making secure communications problematic. Additionally, data centers would face challenges with load balancing and IP address sharing, as these functions rely on resolving domain names to the appropriate IP addresses.
A valid DNS configuration is just as essential as having an internet connection itself.
Why not use DNS?
A DNS client depends on the availability of a DNS server when making a request. For local traffic, this reliance can create a single point of failure or a potential bottleneck.
Do I need to host my own DNS server?
A local DNS server is necessary if workstations communicate using workstation names instead of IP addresses.
Parent topic: Network Infrastructure