I think I'm using ifupdown (it's installed, anyway -- version 0.8.35+b1) but I also believe this is not the root cause of the problem.
It took me awhile to think it through, but if you revisit the problem report, I'm reproducing the problem by running named interactively (on steady-state system) -- so the problem can't be boot-related, as everything else (particularly all of the filesystems, and also all of the network interfaces) is up and running well before the point I attempted to start the daemon. You'd think with all this COVID-19 stay-home stuff going on I would have had time to retest with tracing, but I'm still trying to get a window where I have free time and the rest of my household is willing to take the DNS hit. Thanks, Scott -----Original Message----- From: Michael Biebl <bi...@debian.org> Sent: Tuesday, May 19, 2020 8:43 AM To: 958...@bugs.debian.org; Scott Bailey <sc...@cartasoft.com> Subject: Re: bind9: named fails to start after upgrade to 9.16.2 Could you share your network configuration? Are you using ifupdown? I wonder if this is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960594 where I suspect the if-up.d hook breaking the dependency resolution causing bind9 to be started way too early.
