RH358 – Red Hat Services Management and Automation — Lesson 1: DNS, DHCP, Time, Logging, Printing, and Core Network Services

Learning Objectives

• Interpret the architecture, dependencies, and expected behavior of DNS, DHCP, and chrony.
• Apply central logging and printing services while preserving reviewable technical evidence.
• Recognize and correct the risk where a hidden prerequisite causes the first configuration step to produce an incomplete result.

Detailed Topics

• DNS: apply the concept to a Linux infrastructure team deploying and automating shared enterprise services, record the relevant settings or decisions, and explain the operational consequence.
• DHCP: apply the concept to a Linux infrastructure team deploying and automating shared enterprise services, record the relevant settings or decisions, and explain the operational consequence.
• chrony: apply the concept to a Linux infrastructure team deploying and automating shared enterprise services, record the relevant settings or decisions, and explain the operational consequence.
• central logging: apply the concept to a Linux infrastructure team deploying and automating shared enterprise services, record the relevant settings or decisions, and explain the operational consequence.
• printing services: apply the concept to a Linux infrastructure team deploying and automating shared enterprise services, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates dns, dhcp, time, logging, printing, and core network services by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how a hidden prerequisite causes the first configuration step to produce an incomplete result and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Build a baseline and capture the initial state for DNS, DHCP, Time, Logging, Printing, and Core Network Services. Add verified outcomes to the service configuration portfolio, Ansible automation repository, security evidence, and support runbook.

1. Confirm the scope, versions, access, dependencies, and success criteria.
2. Perform the workflow while recording commands, settings, output, and platform events.
3. Test one expected case and one controlled exception specific to this lesson.
4. Retest the correction and document ownership, rollback, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences DNS in the stated scenario.
• Compare two approaches for central logging and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the service configuration portfolio, Ansible automation repository, security evidence, and support runbook before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, access, dependencies, and starting conditions separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that a hidden prerequisite causes the first configuration step to produce an incomplete result; confirm the cause with a reproducible retest.

Validation Checklist

• The required architecture, access, dependencies, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The service configuration portfolio, Ansible automation repository, security evidence, and support runbook links conclusions to commands, configuration, logs, or other objective evidence.
• Corrective actions, rollback steps, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply DNS, DHCP, Time, Logging, Printing, and Core Network Services, explain the observed Red Hat platform behavior, and support the result with a reviewable service configuration portfolio, Ansible automation repository, security evidence, and support runbook.