It can be set in multiple ways, but basically:
1. Point the WAN DNS server towards your AGH IP (click assign, scroll all the way to the bottom, input AGH ip, hit apply)
2. Go to the DNS redirector, enable it (towards the router or AGH IP) and add an exception for AGH MAC (no redirection or redirect towards an actual public DNS, 8.8.8.8, etc). The last part is to prevent a DNS "loop". If I've understood correctly, the same can be achieved by manually editing /jffs/configs/dnsmasq.conf.add, as well, but I'm not exactly sure on this part.
The main benefit would be filtering the DNS requests coming from the router itself (not only from clients connected to the router). At the same time, it would make it slightly less reliable (if the vm/device running AGH/ pihole crashes your router won't be happy).
1. Point the WAN DNS server towards your AGH IP (click assign, scroll all the way to the bottom, input AGH ip, hit apply)
2. Go to the DNS redirector, enable it (towards the router or AGH IP) and add an exception for AGH MAC (no redirection or redirect towards an actual public DNS, 8.8.8.8, etc). The last part is to prevent a DNS "loop". If I've understood correctly, the same can be achieved by manually editing /jffs/configs/dnsmasq.conf.add, as well, but I'm not exactly sure on this part.
The main benefit would be filtering the DNS requests coming from the router itself (not only from clients connected to the router). At the same time, it would make it slightly less reliable (if the vm/device running AGH/ pihole crashes your router won't be happy).