mhfowler
commented
3 years ago I did some more research into dynamic dns today. A practical need to get it working for the mycodo pub is proving good motivation.
For now, I just connected my pi to duckns, as it was very simple to configure, and was recommended by home-assistant.
It seems the question with dynamicdns for us might be, do we support one provider, a few providers, many providers, or host our own peachcloud-dynamic-dns server somewhere ... it seems to me there isn't a totally decentralized option. Of course, technical users can also setup their own preferred dyndns solution, so maybe we should focus on having one UI based integration for peachcloud for non-technical users. Right now I'd consider duckdns as it was easy. Self-hosting our own peachcloud dyndns server also seems like an interesting option.
Here are the links:
duckdns.org, very easy to install https://www.duckdns.org/install.jsp
home-assistant dynamicdns add-on: https://github.com/home-assistant/addons/blob/master/duckdns/data/run.sh, which uses duckdns
yunohost dynamic dns https://github.com/YunoHost/yunohost/blob/dev/src/yunohost/dyndns.py uses nsupdate https://linux.die.net/man/8/nsupdate
https://www.reddit.com/r/selfhosted/comments/8x8sb1/anyone_host_a_ddns_server_similar_to_duckdns/ self-host ddns with bind?
example of self-hosted DDNS with dreamhost https://github.com/ianloic/dreamhost-ddns
cc @mycognosist
started this issue, in part to just include this research
while looking through yuno host code to see how they do updating, I found the file where they handle dynamic dns, for reference: https://github.com/YunoHost/yunohost/blob/dev/src/yunohost/dyndns.py