The latest release is always available from GitHub at
Install Configure Inadyn Dreambox. 5/26/2017 0 Comments Download DM6. 2 Image Pcd 7. Hi Friends,I wish you all a Very Happy New Year! Addon- manager: Download and install addons. Software: Additinal software items necessary for some plugins. How to install and configure inadyn on CentOS 6. By Jacob Tomlinson on January 5, 2015 under Centos. Install Binary. First we need to download and install the binary. DynDNS makes the utility, along with the source code, available as a zip file which you can download from their website.
/updater/ Dyn Update Clients + API Using an update client with your Remote Access (DynDNS Pro) or Dyn Standard DNS hostname allows you to make sure you can always reach your home network, because it makes sure that your hostname is always up-to-date with the latest IP address. Inadyn is a C based client used to update DNS entries. Inadyn is an IP update client for DynDNS.com, no-ip.com, etc. Why we need this? Well you don’t really need this if you are using static IP. But if you have dynamic IP, you must keep your IP updated with the domain you choose in DynDNS.com or no-ip.com every time you restart the router. Otherwise, the visitors can’t reach to you.
Table of Contents
Introduction
Inadyn is a small and simple Dynamic DNS, DDNS, client with HTTPSsupport. Commonly available in many GNU/Linux distributions, used inoff the shelf routers and Internet gateways to automate the task ofkeeping your Internet name in sync with your public¹ IP address. It canalso be used in installations with redundant (backup) connections to theInternet.
Most people are unaware they share a pool of Internet addresses withother users of the same Internet Service Provider (ISP). Protocols likeDHCP, PPPoE, or PPPoA are used to give you an address and a way toconnect to the Internet, but usually not a way for others to connect toyou. If you want to run an Internet server on such a connection yourisk losing your IP address every time you reconnect, or as in the caseof DHCP even when the lease is renegotiated.
By using a DDNS client like inadyn you can register an Internet namewith a DDNS provider, like FreeDNS. TheDDNS client updates your DNS record periodically and/or on demand whenyour IP address changes. Inadyn can maintain multiple host records withthe same IP address, use a combination of a script, the address from anInternet-facing interface, or default to using the IP address changedetector of the DDNS provider.
__
¹ Public IP address is the default, private addresses can also be used.
Supported Providers
Some of these services are free of charge for non-commercial use, sometake a small fee, but also provide more domains to choose from.
DDNS providers not supported natively like http://twoDNS.de, can beenabled using the generic DDNS plugin. See below for configurationexamples.
- https://www.dyndns.org, https://dyn.com
In-A-Dyn defaults to HTTPS, but not all providers may support this, sotry disabling SSL for the update (ssl = false) or the checkip phase(checkip-ssl = false) in the provider section, in case you run intoproblems.
HTTPS is enabled by default since it protects your credentials frombeing snooped and reduces the risk of someone hijacking your account.
Configuration
In-A-Dyn supports updating several DDNS servers, several accounts even ondifferent DDNS providers. The following /etc/inadyn.conf example showhow this can be done. To verify your configuration, without starting thedaemon, use:
This looks for the default .conf file, to check any file, use:
Example
Notice how this configuration file has two different users of the No-IPprovider -- this is achieved by appending a :ID to the provider name.
We also define a custom cache directory, default is to use /var/cache.In our case /mnt is a system specific persistent store for cachingyour IP address as reported to each provider. Inadyn use this to ensureyou are not locked out of your account for excessive updates, which mayhappen if your device Internet gateway running inadyn gets stuck in areboot loop, or similar.
However, for the caching mechanism to be 100% foolproof the system clockmust be set correctly -- if you have issues with the system clock notbeing set properly at boot, e.g. pending receipt of an NTP message, usethe command line option --startup-delay=SEC. To tell inadyn it isOK to proceed before the SEC timeout, use SIGUSR2.
The last system defined is the IPv6 https://tunnelbroker.net serviceprovided by Hurricane Electric. Here hostname is set to the tunnel IDand password must be the Update key found in the Advancedconfiguration tab.
Sometimes the default checkip-server for a DDNS provider can be veryslow to respond, to this end Inadyn now supports overriding this serverwith a custom one, like for custom DDNS provider, or even a customcommand. See the man pages, or the below section, for more information.
Some providers require using a specific browser to send updates, thiscan be worked around using the user-agent = STRING setting, as shownabove. It is available both on a global and on a per-provider level.
NOTE: In a multi-user server setup, make sure to chmod your .confto 600 (read-write only by you/root) to protect against other usersreading your DDNS server credentials.
Custom DDNS Providers
In addition to the default DDNS providers supported by Inadyn, customDDNS providers can be defined in the config file. Use custom {} ininstead of the provider {} section used in examples above.
In-A-Dyn use HTTP basic authentication (base64 encoded) to communicateusername and password to the server. If you do not have a usernameand/or password, you can leave these fields out. Basic authentication,will still be used in communication with the server, but with emptyusername and password.
A DDNS provider like http://twoDNS.de can be setup like this:
For https://www.namecheap.com DDNS can look as follows. Notice howthe hostname syntax differs between these two DDNS providers. You needto investigate details like this yourself when using the generic/customDDNS plugin:
Here three hostnames are updated, one HTTP GET update request for everyDDNS provider is performed, for every listed hostname. Some providers,like FreeDNS, support setting up CNAME records (aliases) to reduce theamount of records you need to update. FreeDNS even default to linkingmultiple records to the same update, which may be very confusing if youwant each DNS record to be updated from a unique IP address -- make sureto check your settings at the DDNS provider!
Your hostname is automatically appended to the end of the ddns-path,as is customary, before it is communicated to the server. Username isyour Namecheap username, and password would be the one given to you inthe Dynamic DNS panel from Namecheap. Here is an alternative config toillustrate how the hostname setting works:
The generic plugin can also be used with providers that require theclient's new IP address in the update request. Here is an example ofhow this can be done if we pretend that http://dyn.com is notsupported by inadyn. The ddns-path differs between providers and issomething you must figure out. The support pages sometimes list thisunder an API section, or similar.
Here a fully custom ddns-path with format specifiers are used, see theinadyn.conf(5) man page for details on this.
When using the generic plugin you should first inspect the response fromthe DDNS provider. By default Inadyn looks for a 200 HTTP response OKcode and the strings 'good', 'OK', 'true', or 'updated' in theHTTP response body. If the DDNS provider returns something else you canadd a list of possible ddns-response = { Arrr, kilroy }, or just asingle ddns-response = Cool -- if your provider does give any responsethen use ddns-response = '.
If your DDNS provider does not provide you with a checkip-server, youcan use other free services, like http://ipify.org
or even use a script or command:
These two settings can also be used in standard provider{} sections.
Note:hostname is required, even if everything is encoded in theddns-path! The given hostname is appended to the ddns-path used forupdates, unless you use append-myip in which case your IP address willbe appended instead. When using append-myip you probably need toencode your DNS hostname in the ddns-path instead, as is done in thelast example above.
Build & Install
Homebrew (macOS)
To run the latest stable version on macOS, type:
Install Configure Inadyn Downloader
To run the latest version from the master branch, install the git tap instead:
Either of these will install all dependencies.
Building from Source
First download the latest official In-A-Dyn release from GitHub:
In-A-Dyn requires a few libraries to build. The build system searchesfor them, in their required versions, using the pkg-config tool:
- libConfuse (3.0+)
- LibreSSL, OpenSSL, or GnuTLS
They are available from most UNIX distributions as pre-built packages.Make sure to install the -dev or -devel package of the distributionpackages when building Inadyn. On Debian/Ubuntu (derivatives):
To build you also need a C compiler, the pkg-config tool, and make:
When building with HTTPS (SSL/TLS) support, make sure to also installthe ca-certificates package on your system, otherwise Inadyn will notbe able to validate the DDNS provider's HTTPS certificates.
Configure & Build
The GNU Configure & Build system use /usr/local as the default installprefix. In many cases this is useful, but this means the configurationfiles and cache files will also use that same prefix. Most users havecome to expect those files in /etc/ and /var/run/ and configure hasa few useful options that are recommended to use:
You may want to remove the --prefix=/usr option.
SSL/TLS Support
By default inadyn tries to build with GnuTLS for HTTPS support. GnuTLSis the recommended SSL library to use on UNIX distributions which do notprovide OpenSSL/LibreSSL as a system library. However, when OpenSSL orLibreSSL is available as a system library, for example in many embeddedsystems:
To completely disable inadyn HTTPS support (not recommended!):
For more details on the OpenSSL and GNU GPL license issue, see:
RedHat, Fedora, CentOS
On some systems the default configure installation path, /usr/local,is disabled and not searched by tools like ldconfig and pkg-config.So if configure fails to find the libConfuse libraries, or the .pcfiles, create the file /etc/ld.so.conf.d/local.conf with this content:
update the linker cache:
and run the Inadyn configure script like this:
Integration with systemd
For systemd integration you need to install pkg-config, which helpsthe Inadyn build system figure out the systemd paths. When installedsimply call systemctl to enable and start inadyn:
Check that it started properly by inspecting the system log, or:
Building from GIT
If you want to contribute, or simply just try out the latest butunreleased features, then you need to know a few things about theGNU build system:
configure.acand a per-directoryMakefile.amare key filesconfigureandMakefile.inare generated fromautogen.sh,they are not stored in GIT but automatically generated for therelease tarballsMakefileis generated byconfigurescript
To build from GIT; clone the repository and run the autogen.sh script.This requires the GNU tools automake, autoconf and libtool to beinstalled on your system. Released tarballs do not require these tools.
Then you can clone the repository and create the configure script,which is not part of the GIT repo:
Building from GIT requires, at least, the previously mentioned librarydependencies. GIT sources are a moving target and are not recommendedfor production systems, unless you know what you are doing!
Building with Docker
A Dockerfile is provided to simplify building and running inadyn.
Origin & References
Install Configure Inadyn Download Free
This is the continuation of Narcis Ilisei's original INADYN. Nowmaintained by Joachim Nilsson. Please file bug reports, or sendpull requests for bug fixes and proposed extensions at GitHub.