Effective troubleshooting starts with a precise question: how far can the packet travel? Break down the connection to isolate the problem before changing configuration.
1. Define the local network
The IP address and prefix define the network an interface belongs to. With 192.168.10.25/24, the network is 192.168.10.0/24. Traffic for another network follows an appropriate route, often through the default gateway.
2. Separate naming and connectivity
A domain name first needs to resolve to an address. If a connection works by IP but not by name, DNS resolution becomes a troubleshooting lead. You still need to check the protocol, port and filtering rules.
3. Test step by step
Check the interface, addressing, route and remote service. A missing ping response alone does not prove an outage: ICMP may be filtered while an HTTPS service still works.
# Linux — observations sans modification
ip address
ip route
getent hosts example.com
curl -I https://example.comYour turn to build
For a site unreachable by name, propose three distinct hypotheses and a test for each. Explain what each result actually allows you to conclude.
Your discovery progress is saved on this device. You can clear it from My learning.