I am trying to accomplish a task that may, or may not, require a creative solution. Essentially, I want to run my own DHCPd and, more importantly, DNS for my home network.
I want to run my own Name Server for the purpose of having *.local names assigned to our various computers and devices.
I want to run my own DHCP Server so that any computers or devices that access our network will use my name server automatically. My cable modem does not offer this functionality and my "routers" are setup as "dumb" access points.
For example, I don't expect my mother (no offense to moms) to remember an IP Address when she wants to view something shared over the network; or, my sibling may want to play a game on a custom LAN server.
The problem I must absolutely avoid is leaving this system in the hands of other people who live in the building. If the cable modem crashes, they can simply call the Cable Company or restart it when I'm not available. If the Linux system crashes, I need the computers and devices to still retain full access to the Web.
I would like to avoid any ugly solutions such as manually editing 'hosts' files on every device that may ever use the network.
I've tried one application and protocol that would generate *.local domains for each system but it didn't work. Unfortunately, I forget its name.
Does anyone have suggestions on running my own DHCP/DNS and providing a fall-back to my cable modem?
Alternative solutions are welcome as well. I'm sure I'm not the first person to want custom names on a LAN without leaving administration up to people who are neither willing or able. Thanks.
Note: Please do not argue any points related to the usage of TLDs. I understand the risks.
