Linux Issue

Resolver path drift on Linux hosts

Linux name-resolution problems often come from the local resolver model changing underneath the team’s expectations, especially on hosts using `systemd-resolved`, per-link DNS, or persistent `/etc/hosts` overrides.

What It Looks Like

Names resolve differently depending on tool, interface, or format.

Short names fail while FQDNs work, one host resolves correctly while another does not, or shell tools disagree with the application path. These are usually host-side resolver routing issues rather than edge-network failures.

Why It Happens

The host resolver is doing more than teams remember.

  • Search domains and route-only domains change where queries go.
  • The local stub listener abstracts the upstream server view.
  • `/etc/hosts` masks expected network lookups.
  • Single-label names behave differently from FQDNs.