Discussions
Featuure request: When using ctrld on a router, capture the client's IP address in the analytics
The analytics currently record the same IP (the public IP address of the router) for all queries originating from a ctrld daemon running on a router. This is isn't terribly useful.
Web3 Integrations
Is anyone (actually) interested in integration with distributed domain name systems, like:
Feature Request: automatic redirection based on GeoIP?
I'm curious if it's possible to add the ability to use GeoIP data to automatically redirect traffic to a 'local' (to the destination) proxy?
How does ControlD handle Type 65 DNS request?
How does ControlD manage the blocking of Type 65 DNS request.
View IP (Lock Feature)
Is there any way we can lock any specific IP in the view ip in a device. So it doesn't go away.
Router Mode on a Raspberry Pi
Is there a way to manually configure router mode on a raspberry pi so that lan client information (LAN IP, MAC, hostname) is relayed to controlD?
Oblivious DNS-over-HTTPS
Has there been any discussion around implementing Oblivious DNS-over-HTTPS (RFC 9230: https://datatracker.ietf.org/doc/rfc9230/)?
Suggestion
ControlD should handle site scheduling and profile scheduling separately. Currently you have the option of scheduling profiles only. It's great. But you end up being tied to the profile, no matter if you only want to block a few sites, you will have to take ALL the profile along.
Link custom DNS to static IP
Subject says it all.
The list of locations ?
Hello!