On 12.6.2015 16:55, Dan Williams wrote: > On Fri, 2015-06-12 at 10:20 -0400, Matthew Miller wrote: >> On Fri, Jun 12, 2015 at 10:58:14AM +0200, Tomas Hozza wrote: >>> NetworkManager is pure network configuration manager in this scenario. >>> We don't expect nor want NM to handle /etc/resolv.conf. We will only get >>> the current network configuration from it and act upon it. NM >>> configuration will contain "dns=unbound". >> >> Another integration concern: the network config GUI (and ifcfg files, >> for that matter) let me list specific DNS servers. With this >> feature, are those used (and if so, how)? If not, is my configuration >> just silently ignored? > > NM will use those DNS servers as it always has, and with dns=unbound > will simply forward them to unbound, which will use your servers as the > upstream servers. Basically, any information that NM used to write to > resolv.conf will now instead get forwarded to unbound. > > What unbound wants to do with it is another story, of course, that I'm > not an expert on but Thomas/Paul/etc are. This scenario should work fine. Generally we need to get all tools to push the DNS servers to NM (so somewhere else) so the information is available via (e.g.) NM API. That is ideal case which would allow us to centralize DNSSEC handling on one place in dnssec-triggerd. -- Petr Spacek @ Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
