Run cat /etc/resolv.conf.
cat /etc/resolv.conf
Mission 357
DNS and service triage
Separate local name-resolution evidence from web-service health.
Troubleshootingcatgrepsystemctlss
Lesson 357 of 360
0/360 lessons
0/17 missions
Troubleshooting · 8 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
8 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run grep clairos /etc/hosts.
grep clairos /etc/hosts
Run systemctl status nginx.
systemctl status nginx
Run ss -tulpn.
ss -tulpn
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Build repeatable confidence with triaging a name-resolution complaint without assuming a service outage.
Start with cat /etc/resolv.conf, inspect the result, then continue in order.
Triaging a name-resolution complaint without assuming a service outage helps operators explain what they know before they change anything.
- Skipping the output that proves triaging a name-resolution complaint without assuming a service outage.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
cat <file>
Print text file contents.
grep [-i] <text> <file>
Find literal text inside a file.
systemctl status <service>
Inspect simulated service status.
ss|ip
Inspect simulated sockets and addresses.
ssh|scp|ssh-keygen
Practice SSH inspection and dry-run transfer shapes without network access.