I forked nalipaz/hassio-addons because it does not appear to be maintained, and I wanted to add the following functionality:
- fixing a bug, where some characters used in the config where escaped wrongly
Repository of custom addons for hass.io
Inadyn is a small and simple Dynamic DNS, DDNS, client with HTTPS support. Commonly available in many GNU/Linux distributions, used in off the shelf routers and Internet gateways to automate the task of keeping your Internet name in sync with your public IP address.
The objective is to provide a client to do dynamic dns updates on behalf of your hass.io server. The configuration of this addon allows you to setup your provider to dynamically update whenever a change of your public IP address occurs.
The available configuration options are as follows (this is filled in with some example data):
{
"verify_address": false,
"fake_address": false,
"allow_ipv6": true,
"iface": "eth0",
"iterations": 0,
"period": 300,
"forced_update": false,
"secure_ssl": true,
"providers": [
{
"provider": "providerslug",
"custom_provider": false,
"username": "yourusername",
"password": "yourpassword_or_token",
"ssl": true,
"hostname": "dynamic-subdomain.example.com",
"checkip_ssl": false,
"checkip_server": "api.example.com",
"checkip_command": "/sbin/ifconfig eth0 | grep 'inet6 addr'",
"checkip_path": "/",
"user_agent": "Mozilla/5.0",
"ddns_server": "ddns.example.com",
"ddns_path": "",
"append_myip": false
}
]
}
You should not fill in all of these, only use what is necessary. A typical example would look like:
{
{
"provider": "duckdns",
"username": "your-token",
"hostname": "sub.duckdns.org"
}
]
}
or:
{
"providers": [
{
"provider": "someprovider",
"username": "username",
"password": "password",
"hostname": "your.domain.com"
}
]
}
for a custom provider that is not supported by inadyn you can do:
{
"providers": [
{
"provider": "arbitraryname",
"username": "username",
"password": "password",
"hostname": "your.domain.com",
"ddns_server": "api.cp.easydns.com",
"ddns_path": "/somescript.php?hostname=%h&myip=%i",
"custom_provider": true
}
]
}
the tokens in ddns_path are outlined in the inadyn.conf(5)
man page.