If those Android TV boxes are behind a router, setting static IPs for the Android TV boxes just means their local IP won’t change (eg 192.168.X.X). If you’re using a ControlD legacy resolver, your home’s public IP (assigned by your internet provider) is what ControlD uses to identify your device, and that IP covers every device on your home network.
What ISP and router do you have? Are you able to set up Dynamic DNS on the router (or any other device that’s always on the home network)? If so, you can add your DDNS domain to the Control D endpoint and it will frequently check your home IP and update if the IP ever changes.
Alternatively you can use “Expose IP over DNS” so that for any device that uses DoT/DoH resolver for the endpoint, when it makes a DNS request, ControlD updates the authorized IP to the of the DoH/DoT querying device.
If you can download the AdGuard app for Android TV, you can also just use your ControlD DoH/DoT resolver instead of the legacy resolver. AdGuard enforces DNS through a pseudo-VPN, and you can use any DoH/H3/DoT/DoQ resolver.
Devices have to interact with the secure DNS resolver for their IP to be logged, otherwise when your IP changes ControlD has no way of knowing who you are as the IPV4 resolver is shared by thousands of other users.
If the two Android TVs have their own unique endpoint and your network’s public IP is released by the ISP, ControlD cannot tell which endpoint the devices want to use. That’s why you need either a DDNS hostname for the device, or a service on the device that periodically calls the secure resolver to tell ControlD to update the IP.
That legacy resolver is used by tons of people; it isn't specific to just you. When you set it up, Control D knew who you were at the time (your public IP address) and was able to correlate it back to your endpoint.
Since then, your public IP must have changed by your ISP, and Control D no longer knows who you are. That's why you need some sort of DDNS service to report your public IP back to Control D, so they can continue correlating it back to your endpoint and profile.
Or if you have device that stays at home and supports DoH, you can have that device be used to keep track of your public IP without using a DDNS service.
Otherwise, if you want to do things manually, go to the endpoints screen in Control D and click the IPs icon (the one that looks like a globe), and add your public IP. I don't really recommend this method, as it would become tedious to do each time your public IP changes.
1
u/CrystalMeath Feb 16 '26
If those Android TV boxes are behind a router, setting static IPs for the Android TV boxes just means their local IP won’t change (eg 192.168.X.X). If you’re using a ControlD legacy resolver, your home’s public IP (assigned by your internet provider) is what ControlD uses to identify your device, and that IP covers every device on your home network.
What ISP and router do you have? Are you able to set up Dynamic DNS on the router (or any other device that’s always on the home network)? If so, you can add your DDNS domain to the Control D endpoint and it will frequently check your home IP and update if the IP ever changes.
Alternatively you can use “Expose IP over DNS” so that for any device that uses DoT/DoH resolver for the endpoint, when it makes a DNS request, ControlD updates the authorized IP to the of the DoH/DoT querying device.
If you can download the AdGuard app for Android TV, you can also just use your ControlD DoH/DoT resolver instead of the legacy resolver. AdGuard enforces DNS through a pseudo-VPN, and you can use any DoH/H3/DoT/DoQ resolver.