I learned from http://tldp.org/HOWTO/DHCP/x369.html#DHCPSERVER when I got tired of auto-managing IP addresses -- the basic setup is not terrible. If you're using something else for DHCP assignment (e.g. PfSense) you can usually just provide the extra DNS server in the config there and it propagates out.
as you get more experienced it becomes less of "where can I learn x" and more of "how can I do x". You should be able to take a high level concept and look for ways/tools to implement it. For starters, web devs should know about dns. The first step would be, 'install a dns server' and then figuring out as you go. I think the deeper into the rabbit hole you go, the less quality tutorials there are and you have to rely on your problem solving abilities to figure things out.
Comments
Why can't you just push it over dhcp? (This is what I've always done for this use case...)
Thanks for the insight! Its my first time I've setup up something like this (coming from a front end dev background), so I didn't know about dhcp.
Where did you learn to set something up like this?
I learned from http://tldp.org/HOWTO/DHCP/x369.html#DHCPSERVER when I got tired of auto-managing IP addresses -- the basic setup is not terrible. If you're using something else for DHCP assignment (e.g. PfSense) you can usually just provide the extra DNS server in the config there and it propagates out.
as you get more experienced it becomes less of "where can I learn x" and more of "how can I do x". You should be able to take a high level concept and look for ways/tools to implement it. For starters, web devs should know about dns. The first step would be, 'install a dns server' and then figuring out as you go. I think the deeper into the rabbit hole you go, the less quality tutorials there are and you have to rely on your problem solving abilities to figure things out.