A typical symptom is that either accessing the dashboard as
http://hda
or apps that have a web interface (or both) are not reachable and leads to some a site outside your network, on the internet (like amahi.net)
For best results, we recommend that you fully transition your network to using your Amahi server at least for DNS.
:1. [[Turning_off_DHCP_in_your_router|turn off any other DHCP server]] in your network (typically in your router/gateway) and let Amahi handle DHCP so that DNS falls into place automatically.
:2. [[RenewIP|renew Client IP Address]] or reboot '''all''' your client devices. You can do this by turning off the network and turn it back on after a few seconds on your clients (or unplugging it or turning off WiFi for a few seconds, then), so they get a DHCP lease from your HDA, which includes DNS.
:3. turn off the network (WiFi) and turn it back on after a few seconds on your clients, so they get a DHCP lease from your HDA and hence DNS :4. sometimes the clients machine also cache DNS in their browsers. To avoid this, you can hard-refresh the browser, or simply rebootthe machine.
If you have any fixed IP devices in your network from your router settings, these may not pick up a DHCP lease. You may set them up in your HDA under [http://hda/tab/network/hosts Setup > Networking > Fixed IPs].