Birmingham mumbai

[
 260 
]
In this example, the 
/etc/resolv.conf
 output is utilizing servers 
10.10.96.1
 
and 
10.10.96.2
. Therefore, the server will first check 
/etc/hosts
 for a match 
of the resource you're looking up, and if it doesn't find it, it will then check 
/etc/resolv.conf
 in order to find out which server to check next. In this case, 
the server will check 
10.10.96.1
.
The 
/etc/resolv.conf
 file on legacy servers is typically not one that you'd 
make actual changes to, since it's automatically generated by NetworkManager. 
NetworkManager is a service that helps you manage your network interfaces, 
however, it's not used anymore with Ubuntu Server for a handful of releases now. 
Even though you don't typically manually edit the 
/etc/resolv.conf
 file, it may be 
worth looking at on legacy servers to see which DNS servers were assigned, in case 
you're troubleshooting some sort of networking issue.
Nowadays, modern Ubuntu servers utilize 
systemd-resolved
 to handle name 
resolution. If you'd like to see which DNS servers were assigned on a newer Ubuntu 
Server installation, you can simply look at the configuration file for Netplan that we 
worked through earlier in the case of a static IP assignment, but if DHCP is being 
used, the following command will let you know what DNS nameservers your server 
is currently pointing to:
systemd-resolve --status |grep DNS\ Servers
This will provide an output similar to that shown in the following screenshot:
Figure 10.5: Viewing a server's current DNS assignment
In a typical enterprise Linux network, you'll set up a local DNS server to resolve your 
internal resources, which will then forward requests to a public DNS server in case 
you're attempting to reach something that's not internal. We'll get to that in 
Chapter 
11
, 
Setting Up Network Services
, but you should now understand how the name 
resolution process works on your Ubuntu Server.

---

Chapter 10