Setting this object to reset(2) reinitializes the resolver's persistent state as if it had just started, clearing the DNS cache; reading it always returns other(1), regardless of what was last written. Admins use it to force a clean DNS cache, for example after changing DNS server configuration or suspecting stale cached records. Because reads never reflect the write, this is a fire-and-forget command object rather than a status field.