Key | Value |
---|---|
FileName | ./usr/sbin/kres-cache-gc |
FileSize | 17968 |
MD5 | 99E2EAFF528A79056E64A3D6DF6C2904 |
SHA-1 | 20827D197625118F4687C0EC57BE42D8C7F0B21E |
SHA-256 | 350DD7174C03556D326CA505A69F32B3D6C672F52EC2FEC640451BC039352FF1 |
SSDEEP | 192:SnLh8/mkxXnF+a9eUPPZ5W1/If6+rTQ30f/O6XhcAipkxe4BkIV:SLOfVeuPXW1/yrTQEHlRQye5IV |
TLSH | T156820990F3535D23C0D1A376501BDB12E273C044AB9AAF43651CD9611CAFB489FB9B60 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
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 |
---|---|
FileSize | 295644 |
MD5 | AEE4848AF96CD89752981AE635C9D59E |
PackageDescription | caching, 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. |
PackageMaintainer | knot-resolver packagers <knot-resolver@packages.debian.org> |
PackageName | knot-resolver |
PackageSection | net |
PackageVersion | 5.4.2-1 |
SHA-1 | C0590CEA229DAE921615489DE511F77C7E5B4B7F |
SHA-256 | D6E761BC9D18EC47AB8E2382B8F7B97303372ABA8C51749EE92C9E308A09EAB0 |