In-a-Dyn :: DDNS�What and How
Joachim Wiberg
https://github.com/troglobit/inadyn
What is it?
ISPs are everywhere, where their customers are. Many are also DDNS providers.��The client should support as many as possible, and support updating more than one DNS entry.
Tip
In-a-Dyn supports over 30 different providers
In-a-Dyn also supports both IPv4 and IPv6
In-a-Dyn support HTTPS w/ OpenSSL or GnuTLS
You need a DDNS client to actively track any change in your external IP address and then send an update to your DDNS provider(s)
How to use it?
Common Use-case
User has multiple connected sites Each site has a DHCP address
How do we set up a VPN to each site when ISPs can change address at any time?
Solution: DDNS
Sites connect to DDNS provider to keep their DNS entry up-to-date
VPN can be initiated from either end�Usually on-demand service VPNs are used. Works with Roadwarriors too
Protocol
But wait, what about HTTP POST to update?
Cloudflare, Yandex, DNSPod
Use HTTP GET to get IP address and HTTP GET to update the DNS
Dyn.com
Oh Dyn.com get a lot of customers
Let’s copy them!
Every other provider, e.g. Loopia, D.U.I.A., FreeDNS
Sounds simple, let’s wrap curl in a shell script!
Well … scripts work for many use-cases but there are things the DDNS providers don’t want you to know:
Problems
Testing
HTTPS certificates, IPv4 vs IPv6, DDNS providers that block too frequent updates, etc.
How to test this?
You guessed it, manually …
Tip
In-a-dyn has a built-in .conf file validator
In-a-dyn supports custom providers ...
Questions?