privoxy fails to resolve hostnames after update to bullseye
hey,
i used privoxy 3.0.28 with buster (10.11) w/o any problems, but after
upgrading to bullseye (11.2), privoxy 3.0.32 suddenly complains about not
being able to resolve hostnames (see log at the end). the configuration for
privoxy has not changed, and neither have /etc/resolv.conf or /etc/hosts.
on the same host, name resolution works just fine:
> host debian.org
debian.org has address 149.20.4.15
debian.org has address 130.89.148.77
debian.org has address 128.31.0.62
debian.org has IPv6 address 2001:67c:2564:a119::77
debian.org has IPv6 address 2001:4f8:1:c::15
debian.org has IPv6 address 2603:400a:ffff:bb8::801f:3e
debian.org mail is handled by 0 mailly.debian.org.
debian.org mail is handled by 0 muffat.debian.org.
i'd really appreciate it, if someone could enlighten me, where the problem
is
greetings...
privoxy logfile:
2022-02-11 20:53:58.621 9y5ostdB4Ocu Info: Privoxy version 3.0.32
2022-02-11 20:53:58.621 9y5ostdB4Ocu Info: Program name: /usr/sbin/privoxy
2022-02-11 20:53:58.621 9y5ostdB4Ocu Info: Loading filter file:
/etc/privoxy/default.filter
2022-02-11 20:53:58.632 9y5ostdB4Ocu Info: Loading filter file:
/etc/privoxy/user.filter
2022-02-11 20:53:58.633 9y5ostdB4Ocu Info: Loading actions file:
/etc/privoxy/match-all.action
2022-02-11 20:53:58.633 9y5ostdB4Ocu Info: Loading actions file:
/etc/privoxy/default.action
2022-02-11 20:53:58.637 9y5ostdB4Ocu Info: Loading actions file:
/etc/privoxy/user.action
2022-02-11 20:53:58.641 9y5ostdB4Ocu Info: Listening on port 8118 on IP
address 127.0.0.1
2022-02-11 20:53:58.641 9y5ostdB4Ocu Info: Listening on port 8118 on IP
address 10.1.1.10
2022-02-11 20:59:56.757 9y5ostdB4Ocu Request: debian.org:443/
2022-02-11 20:59:56.757 9y5ostdB4Ocu Info: Can not resolve debian.org:
Temporary failure in name resolution
2022-02-11 20:59:56.758 9y5ostdB4Ocu Crunch: DNS failure: debian.org:443
Reply to: