Thanks, I'll try that and try to report. I have already asked on various forums if there is any way to replace /only/ the stub resolver (systemd- resolved) with a more recent version without replacing all the code related to init and the system initialization and been told there is no safe way, hence I understand the fact that ubuntu has a single package for the whole of systemd.
Unfortunately, that means that even if https://launchpad.net/~ubuntu- support-team/+archive/ubuntu/systemd fixes the issue in a vm it will probably be impossible to practically deploy daily updated init, etc on a machine that must be reliably on daily use. On the other side, I have found that it is relatively easy to workaround the issue in systemd-resolved by making the local DNS server slightly deviate from standards so that it responds SERVERFAIL instead of NXDOMAIN for queries in .local. As a final note, as mentioned above, I have moved this discussion by closing this issue and opening a new one, where the problem in systemd- resolved is properly identified. Please see bug 1950850. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950520 Title: systemd-resolved delivers SOA information when it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
