Hello Nick and thanks for this bug report. I didn't try to reproduce your specific issue, however I can see how it can happen. Unfortunately detecting when network is ready is a tricky thing, as the definition of "ready" is not fixed and it's very dependent on the specific configuration of the system.
Implementing a wait/retry mechanism in named could work, but that's out of scope of Ubuntu; my suggestion here is to file an upstream bug. If you do so please link it here so we'll be able to follow it. This said, I think there is room to improve on the "network ready enough" detection mechanism in Ubuntu, and bind9 is not the only package that will benefit for it. I'll discuss the topic with the Server Team. ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
