Johan Ehnberg wrote: > My use case: Johan needs to access his laptop for doing backups and for > remote desktop services. :) > > I can think of a few reasons why resolvconf is suboptimal: > - It is not the standard/recommended solution for DNSSEC, which is optimally > integrated with dhclient > - It requires additional packages for something that should be working already > - It is not supported by canonical > > Also, a few questions arise, mostly from my rather outdated experiences with > resolvconf: > - Would it require modifying the script? > - Would it work with both DHCP and PPP (see my side note)? > - Are all necessary variables available to the script? > - Ease of use: can I simply drop a similar script (which adapts to any host) > in a folder? > - Is it aware of DHCP lease changes (reports new IP) or is it only concerned > with DNS servers changes? > > Resolvconf may well be a good workaround. > > if the resolvconf abilities are not enough you can also stuff in a NM dispatcher.d script (see: /etc/NetworkManager/dispatcher.d/)
-- NetworkManager does not use dhclient-exit-hooks.d, DNSSEC does not work https://bugs.launchpad.net/bugs/293139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
