Course Content
Preparing Our Lab Environment
In this course, we are going configure our lab environment for hands-on practice. We are going to use a virtual machine. This virtual machine can be installed on a Hypervisor like VMWare Workstation, Oracle Virtual Box. It could also be a cloud server hosted in Amazon Web Services, Microsoft Azure, Oracle Cloud Infrastructure (OCI) or in any other cloud provider. For the purpose of this training, we will be using VMWare Workstation PRO as our hypervisor. The main computer system for hands-on learning activities is workstation. Students also use two other machines for these activities: servera and serverb. All three systems are in the lab.uta.com DNS domain. All student computer systems have a standard user account, student, which has the password student. The root password on all student systems is redhat.
0/10
Chapter 1. Introduction to Red Hat Enterprise Linux
While Linux in general offers flexibility, security, and performance, RHEL provides additional enterprise-level features, support, and long-term stability, making it an excellent choice for businesses and large-scale deployments.
0/5
Red Hat System Administration I for Beginners
About Lesson

Configuring Hostnames and /etc/hosts files.

After we have finished installing the three virtual machines to be used in our lab, the next thing is to make sure that the servers can talk to each other and communicate using their IP addresses and hostnames.

IP addresses are not user-friendly for everyday tasks. Instead, people prefer using hostnames rather than numerical strings. Linux provides name resolution mechanisms to map hostnames to IP addresses.

One approach is to manually define static entries for each hostname in the /etc/hosts file of every system. However, this requires updating each server’s hosts file individually.

Alternatively, the Domain Name System (DNS) can be used for name resolution. DNS is a distributed network of servers that maps hostnames to IP addresses and vice versa. For this to function, a system must be configured to contact a nameserver. The nameserver does not need to be on the same subnet, but the system must be able to reach it. Nameserver settings are usually provided via DHCP or configured manually in the /etc/resolv.conf file. Later sections of this chapter will cover the configuration of name resolution in more detail.