Replies: 2 comments 3 replies
-
Try adding the following DHCP options to the configuration file:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
@schzhn Thanks for the reply. If I'm reading the RFC2132 doc correctly for option 15:
That sounds like it's going to give DHCP clients a hint for querying DNS, but won't help any DNS clients that have manual IP address settings, right? Is there a setting on the DNS side of AdGudard Home that will append the local domain name to any unqualified requests? Thanks!! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I can successfully resolve DHCP-assigned local hostnames like
computer1.mylan
, but I would like to also resolvecomputer1
the same way (I want to assume/append .local_domain_name for any unqualified requests). I can't seem to get that to work, and I'm probably just not searching the docs for the correct terminology.I'm new to AdGuardHome, and I'm migrating DNS and DHCP duties from Pi-Hole to AGH. I'm running AGH in a Docker container at
192.168.1.8
and have it configured as the DHCP server for the network, with several static leases. I have my local domain configured:I currently have a simple upstream DNS configuration:
I have tried variations of the below in upstream DNS configuration, but I'm guessing that is causing a recursive loop/timeout.
Most of my searches yield documentation and posts about how to solve this by pointing to a router or some other DHCP server, but I can't seem to find a resolution for using AdGuardHome's DHCP server. Thanks in advance for any help.
Beta Was this translation helpful? Give feedback.
All reactions