Result for 0F95032BC3528B2C9A480CA29FD57CBBCAC4D283

Query result

Key Value
FileName./usr/sbin/kres-cache-gc
FileSize24288
MD5257BCC8E7796A274A6A1DBF8B3B8F057
SHA-10F95032BC3528B2C9A480CA29FD57CBBCAC4D283
SHA-25647191E2093C6152E11561F59BB108526A74E86C5EBF2E128414F8FAB277D589B
SSDEEP384:gVghK/gD0RvhenmAd1W+a39DNkLZJAn+yyA:gKKYD0phen5S+a39DNkLXA+
TLSHT13FB2D693FF05AF23C0D9CF36845B82790A3E8C25E7419313D95C66B51B2BAC85ED944D
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize301280
MD5D0A9A76EC4DDE57B87398D3722304B80
PackageDescriptioncaching, DNSSEC-validating DNS resolver The Knot Resolver is a caching full resolver implementation written in C and LuaJIT, including both a resolver library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides a state-machine like API for extensions. There are three built-in modules - iterator, cache, validator, and many external. . The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the OpenResty of DNS. . The server adopts a different scaling strategy than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.
PackageMaintainerknot-resolver packagers <knot-resolver@packages.debian.org>
PackageNameknot-resolver
PackageSectionnet
PackageVersion5.4.1-2
SHA-14C51D57F275916FBECBAC8BBD9168B8A2D52F7B9
SHA-2567E74BEAA871C6B775F02A8C2B2B0EDCF393838E54AE69AD88ED4B22DDC6999EE