An administrator was told to reverse the search order of a working DNS lookup. During application testing it was discovered that network resolution was not working for the end users. Given the…

An unreachable first DNS server would cause slow lookups or automatic failover to a secondary server, not a total resolution failure for all end users.

The netsvc.conf search order was intentionally reversed per the administrator's instructions, and a correctly reversed entry would still allow resolution to function - the failure points to file accessibility, not search order logic.

The /etc/resolv.conf file must be world-readable for DNS resolution to work for all users; if an administrator modifies the file and inadvertently sets restrictive permissions (such as readable only by root), non-root processes and end-user applications cannot read the DNS server configuration, causing complete resolution failure even when the file content is technically correct.

If the host were not on the network, all network-dependent services would be unavailable, not just DNS resolution, making this an overly broad and unlikely cause.