On Mon, Dec 03, 2007 at 12:56:28PM -0500, Dan Williams wrote: > > NM is going to have to export the DHCP information in any case; the best > option is a pull model where clients can query NM for the DHCP > information they want based on what the current connection is. In the > future, connections may span devices due to > bonding/bridging/connection-sharing or whatever, and the connection is > the thing that gets brought up, not the interface. And since DNS > information is global to the machine (not specific to the interface but > can be tweaked based on _routes_) this requires that programs that want > to know about the DHCP information will need to ask first for the list > of active connections, and second for the DHCP information (if any!) > associated with that connection. When NM gets multiple active device > support, there may be more than one active connection, and each > connection may have DHCP information. Not sure how named would want to > handle those cases. > > Dan > I'm not sure what you mean. NM has to write something into /etc/resolv.conf, right? This decision has to be done on NM side and number of active devices (or connections) has nothing related to that. And this information is exactly what named needs (nameserver statement from resolv.conf). Nothing more (except some notifies when resolv.conf is changed). Adam -- Adam Tkac, Red Hat, Inc. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
