From Amahi Wiki
Steps in troubleshooting the new dnsmasq setup in Amahi 7 or greater (Fedora 19 or greater).
- Check what is in /etc/resolv.conf.
- There should be three lines, something like search YOURHOMEDOMAIN and two with nameserver IP (where IP is the internal IP of your HDA)
- If that is not right, then try restarting hda-ctl, as root and check again:
systemctl restart hda-ctl.service
- See if dnsmasq is running with ps guax | grep dnsmasq
- You should see a line like this: nobody ..... /usr/bin/dnsmasq (where instead of dots you see numbers and a time/date)
- If it's not running for some reason, try restarting it as root with: systemctl restart dnsmasq.service
- Check the dnsmasq configuration files in /etc/dnsmasq.d
- There should be at least three files there: amahi-common.conf, amahi-dhcp.conf and amahi-dns.conf
- There should be some settings in them and they should not mentioned that a service (DNS or DHCP) is not enabled
- In the DNS file, there should be two server lines, with an IP, like this: server=126.96.36.199
- Make sure you can ping those two IP addresses. If not, you have an issue with your routing ... perhaps you cannot reach your router from your HDA?
- Your router address should be in the amahi-dhcp.conf file, in a line like this: dhcp-option=option:router,192.168.1.1
- Make sure the address of your router is proper there
If these configuration parameters are not right, please access your HDA dashboard and access Setup > Network and change accordingly.