Discussions

Issue Description:

The Dynamic DNS field in Controld's Endpoint configuration empties automatically after several weeks of operation, causing DNS filtering to stop working.

Environment:

• Router: TP-Link with native DDNS support
• DDNS Providers tested: tried both TP-Link native DDNS, he.net DDNS
• Monitoring Tool: hetrixtool
• Configuration: Controld Endpoint linked to only this router, no other linked devices

Current Behavior:

1. Dynamic DNS domain is configured correctly in the Controld "Edit Endpoint" window under "Dynamic DNS"
2. Controld DNS filtering works as expected initially without any issue
3. After approximately 2-4 weeks, DNS filtering stops
4. Upon investigation, the Controld "Dynamic DNS" field is found empty!
5. Re-entering the DDNS domain resolves the issue, but...
6. Problem recurs consistently every few weeks

Troubleshooting Steps Taken:

1. Verified router DDNS functionality (confirmed working with no downtime via hetrixtool for months); the DDNS domain always points to my IP.
2. Deleted and recreated Controld endpoint
3. Tested with alternative DDNS provider (he.net)
4. Monitored activity logs from Controld (showing expected logs) every time it is re-configured

Expected Behavior:

The Dynamic DNS field should retain the configured domain name and continue functioning without manual intervention.

Impact:

DNS filtering service interruption requires regular manual reconfiguration to maintain service.

Additional Notes:

• Issue persists across different DDNS providers
• Router DDNS functionality remains stable throughout
• Problem appears isolated to Controld's DDNS parsing system; the Controld "Dynamic DNS" field is emptied every few weeks for unknown reason