reopen 982984 severity 982984 serious thanks Hallo, * Sven Geuer [Sun, Feb 28 2021, 10:20:03PM]:
> Restarting apt-cacher-ng per > > systemctl restart apt-cacher-ng > > temporarily fixes the issue which shows up again after the next boot cycle. > > I also believe apt-cacher-ng should not rely on a nameserver > configuration detected during start-up as /etc/resolv.conf may change > any time, be it for manual re-configuration or for NetworkManager > updating resolv.conf dynamically. Yes. This can be solved by checking for updated resolv.conf at certain moments, for example when a new client connects. However getting the replacement resolver in place is non-trivial because of the shutdown situation. You can grab a copy from https://www.unix-ag.uni-kl.de/~bloch/acng/snap3.6.1/ if you wish, or build from git, or wait a couple of days because I just found an occurrence of #977611 which needs further investigation. Best regards, Eduard. -- <miracee> jaja, irc lerne ich, wenn ich gross bin
signature.asc
Description: PGP signature
