Skip to main content
In this lesson, we introduce DNS on Linux for beginners. We cover basic DNS concepts and demonstrate the essential commands needed to configure and troubleshoot DNS on Linux hosts. By the end, you’ll have the opportunity to complete a hands-on lab with DNS challenges directly in your browser. Imagine you have two computers—A and B—on the same network, with IP addresses 192.168.1.10 and 192.168.1.11 respectively. You can verify connectivity by pinging computer B from computer A using its IP address:
Sample output:
Suppose system B provides database services and you want to refer to it by an easy-to-remember name like “db”. Attempting to ping “db” immediately, however, results in:
To resolve this, add an entry to the /etc/hosts file on system A to map the IP address to the name “db”:
Now, pinging “db” directs traffic to 192.168.1.11:
Keep in mind that system A relies entirely on the /etc/hosts entry for name resolution. It does not verify whether system B’s actual hostname (as reported by the hostname command) matches “db”.
You can also add multiple aliases for the same IP address. For instance, to associate system B with both “db” and “www.google.com”, update the /etc/hosts file as follows:
After this, both names will resolve to 192.168.1.11. Test it with:
Each time you reference a hostname—whether using ping, SSH, or curl—the system first checks the /etc/hosts file:
This translation of a hostname to an IP address is known as name resolution. While managing small networks via local /etc/hosts files works well, maintaining consistency becomes difficult as the number of hosts increases.
If a server’s IP address changes, updating the /etc/hosts file on every host can be a major headache. A centralized DNS server eliminates this problem.

​
Centralizing DNS with a DNS Server

To simplify name resolution in larger networks, you store these mappings on a single DNS server. For example, consider these entries on your centralized DNS server:
Configure each host on your network to use this DNS server for name resolution by specifying its IP address in the /etc/resolv.conf file. For example, if your DNS server’s IP address is 192.168.1.100, add:
The image illustrates a DNS network diagram, showing connections between devices with "eth0" interfaces, IP addresses, and a DNS server within a 192.168.1.0 network.
With this setup, if a hostname isn’t locally resolved via /etc/hosts, the system queries the DNS server. Updating the DNS server’s mappings automatically refreshes host resolution across the network. Local /etc/hosts entries remain useful for specific purposes. For instance, if you provision a test server that only you need to access, add an entry like this:
Output:
The DNS resolution order is controlled by /etc/nsswitch.conf. By default, it is set to:
This configuration instructs the system to check the local /etc/hosts file first (“files”) and then query the DNS server (“dns”). If a hostname isn’t found in either the local file or on the DNS server (for example, www.facebook.com when your DNS does not forward unresolved queries), the ping will fail. To resolve external domains, you can add a public DNS server (such as Google’s 8.8.8.8) to /etc/resolv.conf or set your internal DNS server to forward queries. Consider this scenario: Initially, pinging www.facebook.com fails.
Output:
Once you add the DNS server in /etc/resolv.conf:
Output:
The “.com” indicates a top-level domain (TLD) that classifies the website under specific categories such as commercial or network-related.

​
DNS Hierarchy and Search Domains

Consider the hierarchical structure of Google’s domain. The primary domain is “google.com”, while “www” is one of its subdomains. Other subdomains like maps.google.com, drive.google.com, apps.google.com, and mail.google.com represent different Google services. When queried, your DNS server may need to forward the request up the hierarchy—which involves root DNS servers, TLD servers, and authoritative DNS servers—to resolve the domain to the correct IP address.
The image illustrates the DNS resolution process for "apps.google.com," showing the hierarchy from root DNS to the final IP address, 216.58.221.78.
Similarly, an organization might use a domain such as mycompany.com with subdomains like www.mycompany.com for the public website, mail.mycompany.com for email, drive.mycompany.com for storage, payroll.mycompany.com for payroll services, and hr.mycompany.com for human resources. These DNS records are centrally managed by the internal DNS server. To simplify internal hostname resolution, you can configure a search domain in /etc/resolv.conf. This allows you to use short names instead of fully qualified domain names. For example:
Now, when you ping a short name like “web”, the system automatically appends “mycompany.com” to resolve it:
Output:
Attempting to ping “web” without proper search settings may result in a resolution failure:
Output:
You can also list multiple domains in the search configuration to allow the resolver to try several suffixes for a short hostname.

​
Common DNS Record Types

DNS servers store mappings between hostnames and IP addresses, and these mappings are defined by various record types. Below is a table summarizing common DNS record types: An A record maps a hostname to an IPv4 address, while an AAAA record maps a hostname to an IPv6 address. A CNAME (canonical name) record creates an alias for another domain name—useful for routing multiple names to the same application.
The image shows a table of DNS record types: A, AAAA, and CNAME, with corresponding web-server addresses and IPs.

​
DNS Diagnostic Tools

While ping is a standard tool for checking DNS resolution, utilities like NSLookup and DIG provide more detailed insights. For example, NSLookup directly queries a DNS server, bypassing local /etc/hosts entries:
Sample output:
Similarly, DIG provides comprehensive DNS information:
Sample output:
As you work through practice exercises, you will configure, view, and troubleshoot DNS on actual systems using these tools. That concludes this lesson on DNS. Happy learning!

Watch Video

Practice Lab