Amahi Forums

Background: Before I had my Amahi server set up, I had multiple computers in the house all connected nicely through my router that I flashed with the Tomato firmware. I like this firmware because it is rock solid and very fast, and it makes my home network worry free. One of the things it does is provide DHCP and provides DNS services to all my networked computers (My connected device list is somewhat scary at times).

After I installed the HDA, I decided to keep DHCP on the router and put in a static entry pointing to my HDA server to make it be my DNS box, which worked nicely because it made my installed apps accessible and machine names nice using the home.com domain. Unfortunately I started seeing DNS lookups fail on my desktop machines so I had to revert DNS settings on the router to their prior values to get everyone back online reliably.

What I'm asking for help on is if someone can help direct me on how to instruct my router to redirect all *.home.com requests back to the HDA to service the final name lookups.

Did you modify the DNS settings on your desktop machines to point to your hda?

All my desktop machines get DNS settings from the router (Which continues to serve as the DHCP server)

What I'm hoping for help with is Dnsmasq configuration lines (which I'm not familiar with) that would configure on my network all requests for *.home.com to go with the HDA.

Ok, Update:

I stumbled my way into dnsmasq settings that configured the DNS server on the router to relegate requests for the home.com domain to the HDA. Happy days! Then a storm at our house caused us to lose power and when the HDA came back up, it got the idea in it's head that DHCP should be ON for the HDA, and no matter how many times I turned it off (with the checkbox for the watchdog also unchecked so it would stay off), it would invariably re-start itself. To keep the HDA from stopping everything on the network, I had to shut it down until I could get an idea of what the core problem is.

Any ideas?