Thanks Simon for setting up a reproducer and verifying! @Nick do you agree with Simon's findings, which basically mean that the error this bug report is about is mostly a cosmetic thing, as named will retry?
Anyway, we acknowledge that in general "service X starts before network is ready" is an issue, we have some other bugs in the same category, collected under the network-online-ordering tag: https://bugs.launchpad.net/bugs/+bugs?field.tag=network-online- ordering Thing is, there no general way (that we can see) to implement a "wait for network to be ready" logic, especially given that the concept of "ready" is not well defined and can vary case by case. Being generally more strict is on waiting for networking is certain to produce unwanted side effects in other cases (think of "bind9 never starts" bugs). Waiting for network can only be handled with cooperation with the service in question, which can for example retry on failure, as apparently bind9 does. I'm marking this as Triaged with Low importance (like most other network-online-ordering). ** Changed in: bind9 (Ubuntu) Status: Incomplete => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => Low -- 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
