I have a backup DNS running in the cloud and would like to restrict it, but I don't know the potential range of my ISP in case my IP changes, so I would like to restrict to any IP's that are from a certain domain to let through.
Wouldn't it be easier to list your ISP ranges?
Whois your IP address, find what "org" it belongs to, then query RIPE database to find all subnets that belong to it.
ISP's like comcast have 30 million+ users, and I'm unaware of a way to know which ranges belong to which area, so it'd be hard to limit it that way.
Got it, could you please explain more about this domain idea? Would it somehow point to a dynamic IP?
basically, instead of having to find every *.comcast.net subnet, be able to allow *.comcast.net.
The other idea is to be able to use 'blah.dyndns.org' as a host, instead of an IP, which will resolve to the allowed IP.
Yep, I got the idea.
The problem is that this won't be easy to implement as reverse DNS queries are asynchronous in the current implementation, but let's see how popular this feature request will become.
I need exactly this feature. I have a remote computer I want to use my Adguard Home DNS server on, but the remote computer has a dynamic IP. I set up a dynamic DNS for it and it works well. It would be nice if you could enter the DNS into "allowed clients", then Adguard would use the upstream or bootstrap DNS servers to resolve it and then use the resulting IP as the allowed client.
I would actually prefer to do it via Windows Firewall, but that only allows IP addresses or ranges. It seems like a script should be possible to resolve the dynamic DNS, then update the resulting IP as a firewall rule. But I don't have the skill to write one! :\ _Edit - I found one here: https://bit.ly/2LG30Rz, I'll try it out later._
Voting for this feature!
Why do this? It would be possible to use an own external server on lines with dynamic IP adresses without have DNS services for everybody. Just use a DDNS service and add the hostname in AdGuard Home.
AGH v0.103 allows to set Allowed clients in IP/CIDR format
Most helpful comment
Yep, I got the idea.
The problem is that this won't be easy to implement as reverse DNS queries are asynchronous in the current implementation, but let's see how popular this feature request will become.