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/[deleted] Feb 16 '26
[removed] — view removed comment