Setup help

[mattheys]

Hi all,

I currently use AdGuardHome and I'm happy with the DNS side of things and have a good working failover setup with this using Keepalived.

Unfortunately I can't say the same for DHCP, it's setup and working but only the primary ADH has DHCP enabled and there is no failover or load balancing.

I'd like to create a Gravity cluster to handle DHCP but I also want the DHCP registrations to be added to DNS automatically so I can ping hostname.lan or do a reverse dns lookup. I can see the options to add a PTR server inADH but I'm not sure how best to setup everything up with Gravity in the mix. Should I use Gravity as the main DNS server and have ADH as an upstream, should I use ADH as the main and Gravity as an upstream? I need to have ADH see the clients individual as I have specific ad rules for some devices so I presume that rules out Gravity as the primary DNS server.

I don't really want to get rid of ADH a the moment as it integrates well with Home Assistant and it's easy for me or my wife to turn it off and have it turn itself back on in 30 mins, plus I have it set to block YouTube from midnight to 8pm so the kids don't turn into zombies.

However I do want a redundant DHCP setup where devices register themselves to DNS, to be honest I don't know how the mechanics of that works and if it's a function of a tightly integrated DHCP/DNS server or if it just works with DNS on its own.

[daubman]

I'm also looking to migrate from adguard home to gravity for my home & homelab setup..

It won't be as easy without the provided Home Assistant integration, but you should be able to automate things the same way as you do now via the API.

I think you can use the forward_blocky config string with client groups to achieve your "specific ad rules for some devices" requirement - I need this as well, so at least I am hoping I can get this to work:
https://0xerr0r.github.io/blocky/main/configuration/#client-groups

[mattheys]

Thanks for taking the time to reply, I actually managed to get the two working together quite well.

I setup a DHCP scope and DNS zone called lan. I copied all my DHCP reservations over manually and under the advanced settings of the DHCP scope I set the name_server tagName to my AdGuardHome vIP. Then I also copied over all my DNS rewrites into the DNS zone.

- tagName: router
  value: 192.168.1.1
- tagName: name_server
  value: 192.168.1.100

Then in AGH I set Gravity as the Upstream DNS server for the lan domain.

[/lan/]192.168.1.12
[/*.lan/]192.168.1.12

Apart from what appears to be a long standing issue of DHCP reservations not working correctly, i.e. you set a reservation ip of 192.168.1.10, reboot the device and then it come up with 192.168.1.156 and that also changes in the DHCP reservation page! It's working really well, I haven't looked into how to cluster the DHCP server yet but I like this so far.