On Fri, Jun 12, 2009 at 6:10 AM, Tom Browntom@ng23.net wrote:
Not quite, those can all be inherited on a per-subnet basis. You don't have to do it on a per host basis but that happens to be how the shipping cobbler dhcp templates do it.
do you have an example of how they can be inherited on a subnet basis as seemingly the subnet settings in the template are being ignored ?
I meant that ISC dhcpd allows settings to be inherited on a per-subnet basis. Try commenting out the next-server line in the loop that happens for each host. Then declaring it for the subnet, doing a cobbler sync, and re dhcping. If you tcpdump on ports 67-69 on the dhcp server you should see the traffic exchange from both sides plus the tftp requested files. This is very likely an issue that can be solved by fudging the template a bit.