DNS Client Configuration and Resolution Testing

Introduction

In our last session, we mastered configuring network interfaces for both static and dynamic IP addressing using nmcli. We noted that a complete IP configuration includes the addresses of DNS servers. Today, we'll focus entirely on that piece of the puzzle.

This lesson directly addresses the learning outcome: to configure DNS client settings and test hostname resolution.

Following your preference, we'll first build a solid theoretical foundation of what the Domain Name System (DNS) is and how Linux handles name resolution. Then, we will move into the practical steps of configuring your system's DNS settings using nmcli and, finally, learn how to test that everything is working correctly using standard command-line tools. Understanding DNS is not just crucial for the CompTIA Linux+ exam; it's a fundamental skill for troubleshooting almost any network issue.

1. What is DNS? The Theory of Name Resolution

At its core, networking runs on IP addresses, but humans find it much easier to remember names like google.com or my-internal-server. DNS is the bridge between these two worlds.

To start, let's get a high-level overview of what DNS is and why it's so fundamental to networking from a source you'll appreciate: the CompTIA blog itself.

Now that you have the general concept, let's look at how a Linux system specifically handles the process of name resolution. It's not just about DNS; there's an order of operations.

This next video breaks down the key files involved and the sequence in which Linux consults them.

Key Configuration Files Summary

Based on the video, let's solidify our understanding of these three critical files:

• /etc/hosts: This is a simple text file that acts as a local, static "phonebook." You can add entries here to map an IP address to a hostname. By default, the system checks this file before asking a DNS server. It's useful for overriding public DNS for testing or for defining names for local devices without a DNS server.

  # Example /etc/hosts file
  127.0.0.1   localhost
  192.168.1.100 fileserver.local fileserver
  

• /etc/resolv.conf: This is the primary DNS client configuration file. It tells your system which DNS servers to contact. The most important line in this file is nameserver, followed by the IP address of a DNS server. You can have multiple nameserver lines for primary, secondary, and tertiary servers.

  # Example /etc/resolv.conf file
  nameserver 8.8.8.8
  nameserver 1.1.1.1
  

• /etc/nsswitch.conf: The Name Service Switch (NSS) configuration file is the master controller. It tells the system in what order to use different sources for various types of information. For our purposes, the hosts: line is key. A typical entry looks like this:
  hosts: files dns
  This means: "When trying to resolve a hostname, first look in local files (like /etc/hosts), and if you don't find it there, then ask dns."

2. Configuring DNS Client Settings with NetworkManager

A common mistake for beginners is to directly edit /etc/resolv.conf. On modern Linux systems that use NetworkManager (which we've been using with nmcli), this file is often dynamically generated. Any manual changes you make will be overwritten the next time the network service restarts or a connection is re-established.

The correct, persistent way to configure DNS is to modify the connection profile using nmcli. This ensures your settings survive reboots.

The following video segment shows the exact commands for this process.

Let's walk through a complete example. Suppose we have a connection named enp0s3 and we want to set its DNS servers to Google's (8.8.8.8) and Cloudflare's (1.1.1.1).

1. View your current DNS settings:

   nmcli dev show enp0s3 | grep DNS
   

   This will likely show DNS servers provided by your DHCP server.

2. Modify the connection:
   We will set the DNS servers and, crucially, tell NetworkManager to ignore any DNS servers provided automatically by DHCP.

   sudo nmcli con mod enp0s3 ipv4.dns "8.8.8.8 1.1.1.1"
   sudo nmcli con mod enp0s3 ipv4.ignore-auto-dns yes
   

3. Re-activate the connection to apply the changes:

   sudo nmcli con up enp0s3
   

4. Verify the result:
   Now, if you check the /etc/resolv.conf file, you should see your new settings reflected.

   cat /etc/resolv.conf
   

   The output should now show nameserver 8.8.8.8 and nameserver 1.1.1.1.

3. Testing Hostname Resolution

Once your DNS settings are configured, you need to test them. While ping <hostname> is a good first step, it doesn't give you much detail. For proper DNS troubleshooting, Linux provides several powerful utilities.

Here are the main tools you should know for the Linux+ exam:

The dig command is particularly important. Its output is broken into sections that give you a complete picture of the DNS query.

Conclusion

Excellent work today! You've successfully navigated the essentials of DNS client configuration and testing on a Linux system.

Key Takeaways:

• DNS is the service that translates human-friendly hostnames into machine-usable IP addresses.
• Linux uses a sequence of sources for resolution, configured in /etc/nsswitch.conf (typically checking local /etc/hosts first, then DNS).
• The /etc/resolv.conf file shows the current nameservers but should not be edited directly on modern systems managed by NetworkManager.
• The correct, persistent method for setting DNS client information is with nmcli connection modify <name> ipv4.dns "..." and ipv4.ignore-auto-dns yes.
• The dig, nslookup, and host commands are the standard tools for testing and troubleshooting DNS resolution.

Preview of the Next Lesson:

Now that we can configure an interface with an IP address and resolve hostnames, the next piece of the networking puzzle is understanding how your system decides which path to take to reach other networks. In our next lesson, we will manage the system's routing table, giving you a complete picture of how IP traffic gets from your machine to its destination.