{% blocktrans trimmed %} Usually, you should configure one system on your network to update the DNS. This can be either your router or a host on your network and it will run some software called the update client. {% endblocktrans %}
{% blocktrans trimmed %} We have some specific configuration hints for some devices and update clients, please see the tabs above. If you don't find yours there, use the generic hints below. {% endblocktrans %}
{% blocktrans trimmed %}
Important note about security and compatibility:
For update URLs, we always give the https (not: http) URL as that will use an encrypted connection
to transfer your data (including your update secret). Depending on your update client (router firmware or
PC software) and the specific nsupdate.info-based service, https might be not supported.
So, if it does not work, you have the choice of using a different update client and/or a different service,
or transmitting your data using an unencrypted connection (using http: instead of https:).
{% endblocktrans %}
On {{ WWW_HOST }} https is {% if not WE_HAVE_TLS %}not {% endif %}supported.
{% trans "Your update client needs to access the following URLs to update the DNS:" %}
{% trans "For IPv4 updates:" %} {% trans "For IPv6 updates:" %} {% blocktrans trimmed %} The IPs will be determined automatically using the remote address our service is seeing (see below for more details). {% endblocktrans %}{% trans "Your update client has to do the following steps:" %}
| Setting | Value |
|---|---|
| Dynamic DNS provider | Custom |
| Update-URL | https://{{ WWW_IPV4_HOST }}/nic/update |
| Domain Name | {{ host.get_fqdn|default:"<your hostname>" }} |
| User name | {{ host.get_fqdn|default:"<your hostname>" }} |
| Password | {{ update_secret|default:"<your secret>" }} |
| Setting | Value |
|---|---|
| DDNS Service | Custom |
| DYNDNS Server | {{ WWW_IPV4_HOST }} |
| Username | {{ host.get_fqdn|default:"<your hostname>" }} |
| Password | {{ update_secret|default:"<your secret>" }} |
| Hostname | {{ host.get_fqdn|default:"<your hostname>" }} |
| URL | /nic/update? |
| Additional DDNS Options | {% trans "(leave this field empty)" %} |
| Do not use external ip check | Yes |
| Force Update Interval | 7 |
{% trans "ddclient is a popular dyndns update daemon on Linux." %}
# /etc/ddclient.conf
# this will update your ipv4 address to the address
# the web service sees requests coming from:
protocol=dyndns2
use=web, web=http://{{ WWW_IPV4_HOST }}/myip
ssl=yes # yes = use https for updates
server={{ WWW_IPV4_HOST }}
login={{ host.get_fqdn|default:"<your hostname>" }}
password='{{ update_secret|default:"<your secret>" }}'
{{ host.get_fqdn|default:"<your hostname>" }}
# ddclient releases <= 3.8.1 do not support IPv6,
# but there is a patch for IPv6 from Eduardo Trapani.
# using such a patched ddclient, the following should work:
#
# this will update your IPv6 address to the interface address:
#protocol=dyndns2
#usev6=if, if=eth0
#ssl=yes # yes = use https for updates
#server={{ WWW_IPV6_HOST }}
#login={{ host.get_fqdn|default:"<your hostname>" }}
#password='{{ update_secret|default:"<your secret>" }}'
#{{ host.get_fqdn|default:"<your hostname>" }}
Homepage: http://m0n0.ch/wall
| Setting | Value |
|---|---|
| Service Type | DynDNS |
| Hostname | {{ host.get_fqdn|default:"<your hostname>" }} |
| Server | {{ WWW_IPV4_HOST }} |
| Username | {{ host.get_fqdn|default:"<your hostname>" }} |
| Password | {{ update_secret|default:"<your secret>" }} |
# /etc/inadyn.conf
logfile /var/log/inadyn/inadyn.log
verbose 5
period 300
system ipv4@nsupdate.info
ssl
username {{ host.get_fqdn|default:"<your hostname>" }}
password {{ update_secret|default:"<your secret>" }}
alias {{ host.get_fqdn|default:"<your hostname>" }}
# note: no IPv6 support in inadyn yet.
# ddns-scripts configuration /etc/config/ddns
config service "ipv4ddns"
option enabled "1"
option interface "wan"
option use_syslog "1"
option service_name "{{ WWW_HOST }}"
option update_url "http://[USERNAME]:[PASSWORD]@{{ WWW_IPV4_HOST }}/nic/update?hostname=[DOMAIN]&myip=[IP]"
option ip_source "web"
option ip_url "http://{{ WWW_IPV4_HOST }}/myip"
option domain "{{ host.get_fqdn|default:"<your hostname>" }}"
option username "{{ host.get_fqdn|default:"<your hostname>" }}"
option password "{{ update_secret|default:"<your secret>" }}"
# for https support, first install wget with ssl support and
# a current (and working) bundle of CA certificates:
# opkg install wget
# mkdir -p /etc/ssl/certs
# wget -P /etc/ssl/certs http://curl.haxx.se/ca/cacert.pem
option use_https "1"
option cacert "/etc/ssl/certs/cacert.pem"
Homepage: https://www.pfsense.org
{% blocktrans trimmed %} Please note: if the pfSense WAN interface does not have your public IP and does not notice your public IP changing, the update will be done delayed (default: daily at 01:01). You can tweak this by editing /etc/crontab from where it invokes /etc/rc.dyndns.update - but be careful: do not invoke it too frequently and consider that this applies to all your DDNS updaters. {% endblocktrans %}
| Setting | Value |
|---|---|
| Disable | {% trans "(do not select this)" %} |
| DDNS Service | Custom |
| Interface to monitor | WAN {% trans "(most likely)" %} |
| Interface to send from | WAN {% trans "(most likely)" %} |
| Verbose logging | {% trans "(select this as long as you need it)" %} |
| Username | {{ host.get_fqdn|default:"<your hostname>" }} |
| Password | {{ update_secret|default:"<your secret>" }} |
| Update URL | https://{{ WWW_IPV4_HOST }}/nic/update |
| Result Match | good|nochg |
| Description | update DDNS host with IP v4 address |