resolv is Ruby’s thread-aware DNS resolver library, shipped as part of the language’s default gem ecosystem. It provides name resolution functions that applications can use instead of, or alongside, the operating system’s normal socket resolver. In practice, that means Ruby code can inspect hostnames, perform custom lookups, or redirect resolution through resolv-replace.
In security work, resolver libraries matter because DNS often sits on a trust boundary. If an application uses resolv for hostname validation, outbound allowlists, redirects, or webhook checks, bugs in the resolver can cause denial of service, memory pressure, or mismatches between what the app thinks it verified and what actually gets resolved. Defenders should inventory whether critical code paths depend on Resolv, patch the runtime, and test that DNS-based policy decisions still behave as expected.