Hi Tim, I had the same issue with container running on the system. In my case the DNS runs on the same box and the container was broken until I switched its network mode to host and forced it to use gateway as DNS instead of local IP (which is basically a loopback). I've checked that a few times, same result. Changing solely the network mode or the DNS IP wasn't enough. Apart from the mentioned container, I hadn't experienced any issues, but it may be as well that the devices that couldn't retrieve addresses from said box due to the bug simply switched to another DNS that I have (and it's not running on Ubuntu).
I've just rolled back to -94 and everything went back to normal. I run plenty of containers and just one had encountered this kind of issue with resolver (the host itself was running just fine). Due to that I've bumped into a thread on Home Assistant on git, where people found out that this is kernel-related (https://github.com/home- assistant/core/issues/162636). It could be that this surfaces in some, certain situations. If it caused widespread DNS resolution issues, I'm betting there wouldn't be seeing a single thread with just a handful of posts. ** Bug watch added: github.com/home-assistant/core/issues #162636 https://github.com/home-assistant/core/issues/162636 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141531 Title: Network unstable on 6.8.0-100.100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141531/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
