SSH works by IP but not by hostname
This issue matters because it looks like an access problem while the SSH service and network path may already be healthy. The real break is often in how the client resolves the name it is trying to use.
Transport succeeds, admin workflow still fails.
Operators can connect directly to an IP address, but the same host fails when accessed through a short name or alias. That usually points away from the daemon itself and toward local resolution, search domains, or host key mismatch introduced by naming changes.
Name handling and trust handling get mixed together.
- Short names no longer map through the expected search domain.
- Resolver behavior changed after DHCP or host configuration updates.
- `/etc/hosts` or stale aliases override intended DNS behavior.
- Host key warnings create noise around what is actually a naming issue.