Setting Adguard Home as DHCP Server. Questions on how to manage Static IP and DNS

  • Running Adguard Home and Unbound on DietPi.
  • DHCP Reservation set on the router for dietpi.
  • Dietpi ip is set as DNS server in router
  • Switched from DHCP to Static IP eth0 routing within Dietpi-config
  • Turn off DHCP Server on router and turn on DHCP Server of Dietpi

My dietpi-config for eth0 is shown as follows:
Mode: Static
IP: x.x.x.xyz
Static Mask: 255.255.255.0
Static Gateway: x.x.x.1
Static DNS: x.x.x.1

Where I’m confused is in moving Adguard to be the DHCP Server instead of the router.

Do I need to adjust to static DNS settings within the router for Dietpi since I will lose the DHCP reservation?
Do I need to adjust the static dns settings for Dietpi?
If I turn off DHCP Server functionality in the router, then turn on DHCP Server in Adguard, is that enough for these services to keep knowing where each other are?

Thanks! Looking to clarify what I’m doing a little bit before I make a major networking change.

I don’t think you need to change anything on the router except switching off DHCP. The rest should be managed by AGH DHCP server.

Important to have STATIC IP configuration on DietPi themselves, and a global public DNS set. Best practice is his to use AGH DNS within DietPi own settings.

1 Like

Where would this be defined? In Adguard Home or in the router as well?
I’m guessing it would be find in upstream dns providers.

Static IP is currently set in DietPi, but not on the Orbi router. I see I can set a static route on the router with:

Route Name
  • |Private|
  • |Active|
    |Destination IP Address|…|
    |IP Subnet Mask|…|
    |Gateway IP Address|…|
    |Metric|

My internet is being received by a fiber modem, while is assigned to Passthrough all traffic to the router IP. fyi.

Again, there is nothing to set or adjust on your router. Just disable DHCP. Within DietPi configuration settings, where you set STATIC IP, you can set upstream DNS. This has nothing to do with AGH, it’s DietPi own setting.

So, it is failing. The enable dhcp server button refuses to work, even after successfully confirming no other dhcp server on the network. Looked on github and found an issue filed related to Bookworm release not enabling the button.

Something we can’t help with as this is outside our control. You would need to wait on AGH to fix this.

Was able to resolve it by selecting Reset Settings and then manually entering all of the interface info Adguard displays into each field and then clicking save.

After this, enable button worked.

Thanks.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.