Difference between revisions of "Dynamic DNS"
(→ddclient: don't compare services, only describe configuration, afraid-dyndns-uv is abandoned) |
|||
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Domain Name System]] | [[Category:Domain Name System]] | ||
[[ja:ダイナミック DNS]] | [[ja:ダイナミック DNS]] | ||
− | + | According to [[Wikipedia:Dynamic DNS|Wikipedia]]: | |
− | + | :'''Dynamic DNS''' ('''DDNS''' or '''DynDNS''') is a method of automatically updating a [[Wikipedia:name server|name server]] in the [[Wikipedia:Domain Name System|Domain Name System]] (DNS), often in real time, with the active DDNS configuration of its configured hostnames, addresses or other information. | |
− | + | :The term is used to describe two different concepts. The first is "dynamic DNS updating" which refers to systems that are used to update traditional DNS records without manual editing. These mechanisms are explained in [[RFC:2136|RFC 2136]], and use the [[Wikipedia:TSIG|TSIG]] mechanism to provide security. The second kind of dynamic DNS permits lightweight and immediate updates often using an update client, which do not use the RFC2136 standard for updating DNS records. These clients provide a persistent addressing method for devices that change their location, configuration or [[Wikipedia:IP address|IP address]] frequently. | |
+ | |||
+ | For RFC2136 there is {{man|1|nsupdate}} from {{Pkg|bind-tools}}. For dynamic DNS services there are several packages available, see [[#Update clients]]. | ||
+ | |||
+ | == Router == | ||
If the device needing DDNS sits behind a router, you should first check if the router itself can update any DDNS services. Although the selection of services may be limited, there are several advantages to using the router: it will probably be easier to set up, will require little to no maintenance, and will have no downtime (if the router is down you won't have Internet anyway). | If the device needing DDNS sits behind a router, you should first check if the router itself can update any DDNS services. Although the selection of services may be limited, there are several advantages to using the router: it will probably be easier to set up, will require little to no maintenance, and will have no downtime (if the router is down you won't have Internet anyway). | ||
+ | |||
+ | == Update clients == | ||
+ | |||
+ | Note that some dynamic DNS providers do not require a dedicated client and can be updated with {{Pkg|curl}}. | ||
+ | |||
+ | === Multi-service clients === | ||
+ | |||
+ | * {{App|ddclient|Update dynamic DNS entries for accounts on many dynamic DNS services.|https://github.com/ddclient/ddclient|{{Pkg|ddclient}}}} | ||
+ | * {{App|inadyn-fork|Dynamic DNS client with SSL/TLS support.|http://troglobit.com/inadyn.html|{{AUR|inadyn-fork}}, {{AUR|inadyn-fork-git}}}} | ||
+ | * {{App|inadyn-mt|A simple dynamic DNS client based on inadyn.|http://inadyn-mt.sourceforge.net/|{{AUR|inadyn-mt}}}} | ||
+ | * {{App|ndyndns|Supports DynDNS and Namecheap.|https://github.com/niklata/ndyndns|{{AUR|ndyndns}}}} | ||
+ | |||
+ | === Single-service clients === | ||
+ | |||
+ | * {{App|duckdns|Update your DuckDNS.org entries from your computer with systemd.|https://www.duckdns.org/|{{AUR|duckdns}}}} | ||
+ | * {{App|noip|Dynamic DNS Client Updater for no-ip.com services.|3=http://www.no-ip.com/downloads.php?page=linux|4={{AUR|noip}}}} | ||
+ | * {{App|petrified|Bash client to update dynamic DNS at freedns.afraid.org.|https://gitlab.com/troyengel/petrified|{{AUR|petrified}}}} | ||
=== ddclient === | === ddclient === | ||
Line 20: | Line 41: | ||
|+ ddclient compatible services | |+ ddclient compatible services | ||
! Service | ! Service | ||
− | |||
− | |||
− | |||
! Config Notes | ! Config Notes | ||
− | |||
|- | |- | ||
! [http://now-dns.com/ Now-DNS] | ! [http://now-dns.com/ Now-DNS] | ||
− | + | | [https://now-dns.com/client/ddclient.conf example] | |
|- | |- | ||
! [http://www.changeip.com/ ChangeIP] | ! [http://www.changeip.com/ ChangeIP] | ||
− | + | | [https://sourceforge.net/p/ddclient/wiki/protocols/#changeip example] | |
− | |||
− | |||
− | |||
|- | |- | ||
! [https://www.duckdns.org/ Duck DNS] | ! [https://www.duckdns.org/ Duck DNS] | ||
− | + | | [https://sourceforge.net/p/ddclient/wiki/protocols/#duckdns example] | |
|- | |- | ||
! [http://freedns.afraid.org/ FreeDNS] | ! [http://freedns.afraid.org/ FreeDNS] | ||
− | + | | [http://freedns.afraid.org/scripts/freedns.clients.php example] | |
|- | |- | ||
! [http://www.noip.com/ No-IP] | ! [http://www.noip.com/ No-IP] | ||
− | + | | Use protocol {{ic|noip}}, server {{ic|dynupdate.no-ip.com}} | |
|- | |- | ||
! [https://www.nsupdate.info/ nsupdate.info] | ! [https://www.nsupdate.info/ nsupdate.info] | ||
− | + | | Use protocol {{ic|dyndns2}} | |
|- | |- | ||
! [https://dyn.com/dns/ Dyn DNS] | ! [https://dyn.com/dns/ Dyn DNS] | ||
− | + | | [https://sourceforge.net/p/ddclient/wiki/protocols/#dyndns2 example] | |
|- | |- | ||
! [https://www.namecheap.com/ Namecheap] | ! [https://www.namecheap.com/ Namecheap] | ||
− | + | | [https://sourceforge.net/p/ddclient/wiki/protocols/#namecheap example] | |
− | |||
|- | |- | ||
! [https://www.dynu.com/ Dynu] | ! [https://www.dynu.com/ Dynu] | ||
− | + | | [https://www.dynu.com/DynamicDNS/IPUpdateClient/DDClient example] | |
− | |||
|} | |} | ||
{{Note| Free users of no-ip are required to manually confirm their domain(s) every 30 days. Domain confirmation is not required for Enhanced users though. More info at [http://www.noip.com/support/knowledgebase/why-is-my-hostname-pending-deletion/ Why is My Hostname Pending Deletion?]}} | {{Note| Free users of no-ip are required to manually confirm their domain(s) every 30 days. Domain confirmation is not required for Enhanced users though. More info at [http://www.noip.com/support/knowledgebase/why-is-my-hostname-pending-deletion/ Why is My Hostname Pending Deletion?]}} | ||
Line 81: | Line 93: | ||
Additional configuration for {{ic|network-online.target}} may be necessary, see [https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget#cutthecraphowdoimakenetwork.targetworkforme]. | Additional configuration for {{ic|network-online.target}} may be necessary, see [https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget#cutthecraphowdoimakenetwork.targetworkforme]. | ||
− | |||
− | |||
− | |||
− | |||
== Other providers == | == Other providers == | ||
− | + | Other DDNS providers are not compatible with [[#ddclient|ddclient]] so updating your IP with them may require a special tool or some custom scripting. Remember that if the service allows you to update your IP using the command line, you can automate the process using tools such as [[cron]] or [[systemd/Timers]]. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 05:11, 9 October 2018
According to Wikipedia:
- Dynamic DNS (DDNS or DynDNS) is a method of automatically updating a name server in the Domain Name System (DNS), often in real time, with the active DDNS configuration of its configured hostnames, addresses or other information.
- The term is used to describe two different concepts. The first is "dynamic DNS updating" which refers to systems that are used to update traditional DNS records without manual editing. These mechanisms are explained in RFC 2136, and use the TSIG mechanism to provide security. The second kind of dynamic DNS permits lightweight and immediate updates often using an update client, which do not use the RFC2136 standard for updating DNS records. These clients provide a persistent addressing method for devices that change their location, configuration or IP address frequently.
For RFC2136 there is nsupdate(1) from bind-tools. For dynamic DNS services there are several packages available, see #Update clients.
Contents
Router
If the device needing DDNS sits behind a router, you should first check if the router itself can update any DDNS services. Although the selection of services may be limited, there are several advantages to using the router: it will probably be easier to set up, will require little to no maintenance, and will have no downtime (if the router is down you won't have Internet anyway).
Update clients
Note that some dynamic DNS providers do not require a dedicated client and can be updated with curl.
Multi-service clients
- ddclient — Update dynamic DNS entries for accounts on many dynamic DNS services.
- inadyn-fork — Dynamic DNS client with SSL/TLS support.
- inadyn-mt — A simple dynamic DNS client based on inadyn.
- ndyndns — Supports DynDNS and Namecheap.
Single-service clients
- duckdns — Update your DuckDNS.org entries from your computer with systemd.
- noip — Dynamic DNS Client Updater for no-ip.com services.
- petrified — Bash client to update dynamic DNS at freedns.afraid.org.
ddclient
ddclient is compatible with many DDNS services and is the recommended tool for updating DDNS if your router is not an option. It includes systemd support.
After installing, edit the default config /etc/ddclient/ddclient.conf
to set up your DDNS provider (it includes many examples). Then enable and start ddclient.service
.
Some of the compatible services are listed below, but you can also check the examples and protocols for more.
Service | Config Notes |
---|---|
Now-DNS | example |
ChangeIP | example |
Duck DNS | example |
FreeDNS | example |
No-IP | Use protocol noip , server dynupdate.no-ip.com
|
nsupdate.info | Use protocol dyndns2
|
Dyn DNS | example |
Namecheap | example |
Dynu | example |
Use an external website to determine IP address
If ddclient is unable to detect your IP address, you can configure ddclient to fetch your IP from an external webpage such as whatismyip.org. Add somewhere in the config file:
/etc/ddclient/ddclient.conf
# use whatismyip.org to determine IP address use=web web=whatismyip.org
Starting ddclient after networking is up
If you find that ddclient is unable to update your IP properly, it may be that the ddclient process is starting before networking is up. To fix it, you can edit the unit file to depend on network-online.target
:
# systemctl edit ddclient.service
[Unit] After=network-online.target Wants=network-online.target
Additional configuration for network-online.target
may be necessary, see [1].
Other providers
Other DDNS providers are not compatible with ddclient so updating your IP with them may require a special tool or some custom scripting. Remember that if the service allows you to update your IP using the command line, you can automate the process using tools such as cron or systemd/Timers.