Linux Survival Basics
Read-onlyRead systemd-resolved Status
You need resolver state while checking network reachability.
Command
resolvectl statusBefore you run this
System impact: Read-only. Low when scoped to the shown target.
When not to use it: Do not edit resolv.conf before confirming the active resolver manager.
Expected output
Global and per-link DNS servers, search domains, and protocol state.
System impact
Read-only. Nothing changes. The command reads current state and prints diagnostic evidence.
Recovery / rollback: no state is changed.
When to use it
Use when route and DNS symptoms overlap.
When not to use it
Do not edit resolv.conf before confirming the active resolver manager.
Example run
Commands shown
These are the commands shown for inspection. Treat them as an example, not proof that your system will behave identically.
resolvectl statusresolvectl status
next steps
Related commands
Read One systemd Timer Status
Timer status shows whether the schedule is loaded and active.
systemctl status backup.timer --no-pager
Read the Failure Cause in systemctl Status
The status page often tells you the failed startup step before you open every log.
systemctl status app-worker --no-pager --lines=50
Check logrotate Timer Status
The timer may be disabled, missed, or failing.
systemctl status logrotate.timer --no-pager
Show NetworkManager Device State
NetworkManager may know why the interface is disconnected.
nmcli device status
Inspect One Service Without Pager Traps
Make systemctl status safe for scripts, screenshots, and quick incident notes.
systemctl status nginx --no-pager --lines=30
next diagnostic step
Where to go from this command
- Default route missing hub Use after route/address checks when DNS symptoms remain.
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.