Hi @lzap,
I can totally agree with keeping Foreman out of the business of actually writing dhcpd.conf or named.conf (for that matter) files via a few clicks in the webUI. I can’t really recommend what the best route would be…Having the installer be able to create a “get me started” dhcp/dns config that foreman can work with is awesome. On the other hand, having the installer (or foreman as a whole) be able to setup whatever dhcp/dns configuration an admin can dream up seems out of scope to me.
FWIW, I don’t have much complaint on how things work, I’ve been involved in this community for 6-7 years now, and was a Satellite 5 customer before that. My current role deals with introducing Foreman to both Admins and Managers around my organization who have never seen it and might not even be familiar with PXE/kickstart/preseed processes. You might think of our enterprise as being a highly distributed IT environment where each department has it’s own IT group, which does not report up to or through the enterprise group. I don’t know if that’s unique or not, but the disconnect/confusion I described is common when I do I live demo of provisioning. I know this from the kinds of questions I get back from admins who end up playing with foreman on their own after I introduce it to them.