[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to request a feature or enhancement and not ask a question
The problem
When you set the local_domain_name — The domain name that AdGuard Home's DHCP server uses for hostnames of its clients. The default value, which is also set when this value is empty, is lan. So, if you have a machine called myhost in your network, and AdGuard Home is this network's DHCP server, the hostname of that machine is myhost.lan.
DNS queries of type A for such hosts are only allowed from locally served networks, such as 10.0.0.0/8, 192.168.0.0/16, and so on. Other clients receive an empty NXDOMAIN response.
But I'm using the DHCP server on a public subnet (with public IPs).
When i set the local_domain_name with the actual public domain name, then all DNS request for the DCHP names
and specially the dns names for DHCP static leases (servers) are not resolved and the DHCP clients get an empty NXDOMAIN response.
Proposed solution
Please add a optional toggle for enabling of resolving the DHCP names with public domain names on public networks.
And maybe a input box allowing to specify which networks are allowed to get a proper response for the A queries on those DHCP names with the attached local domain name.
Alternatives considered and additional information
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to request a feature or enhancement and not ask a question
The problem
When you set the local_domain_name — The domain name that AdGuard Home's DHCP server uses for hostnames of its clients. The default value, which is also set when this value is empty, is lan. So, if you have a machine called myhost in your network, and AdGuard Home is this network's DHCP server, the hostname of that machine is myhost.lan.
DNS queries of type A for such hosts are only allowed from locally served networks, such as 10.0.0.0/8, 192.168.0.0/16, and so on. Other clients receive an empty NXDOMAIN response.
But I'm using the DHCP server on a public subnet (with public IPs). When i set the local_domain_name with the actual public domain name, then all DNS request for the DCHP names and specially the dns names for DHCP static leases (servers) are not resolved and the DHCP clients get an empty NXDOMAIN response.
Proposed solution
Please add a optional toggle for enabling of resolving the DHCP names with public domain names on public networks. And maybe a input box allowing to specify which networks are allowed to get a proper response for the A queries on those DHCP names with the attached local domain name.
Alternatives considered and additional information
Thanks in advance