This list was really helpful for me getting started and learning about
knot-resolver. I want to say thanks,
and return the favor by open-sourcing the config files
and scripts I ended up with.
serves as an other example of a working configuration, with
some additional capabilities:
contains a few useful bash/zsh functions
(clear cache, override forwarding, reset forwarding, dump stats, ...)
installation instructions with a little more detail than I found
elsewhere, including how to find/update the URLhaus abuse.ch database,
how to generate the certificate file, and a couple tricks for
dealing with captive portals
tkrizekOBS is a huge mess when it comes to details like this. It's the reason their Arch packages are unusable..
tkrizekIt might also be some transient artifact caused by out of sync metadata vs published packages.
File has unexpected size (293436 != 293328). Mirror sync in progress? [IP: 220.127.116.11 9999] Hashes of expected file: - SHA256:68d47a8488987a9da8a3ea89523f92a67415bc8c2f8f3ed2f66817f3f1697a2d - SHA1:d272ecc5c32c0e4c1256fa99a63c019a53df8eb9 [weak] - MD5Sum:001f79ad908b7b65df715b7cea1d24c0 [weak] - Filesize:293328 [weak]
knot-resolversection, and find the Size that is listed
tkrizekWhen I download the package directly from https://build.opensuse.org/package/binaries/home:CZ-NIC:knot-resolver-latest/knot-resolver/Debian_10 it has the right size, so there might be some OBS issues with mirror synchronization. I'd give it a few hours
tkrizekAll the mirrors seem to have the same issue according to https://download.opensuse.org/repositories/home:/CZ-NIC:/knot-resolver-latest/Debian_10/amd64/knot-resolver_5.1.3-1_amd64.deb.mirrorlist
tkrizek@micah_gitlab have you seen this issue before or was this the first time it happened?