2 <!DOCTYPE refentry PUBLIC
"-//OASIS/DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
5 <refentry id=
"ddns.conf">
7 <title>ddns.conf
</title>
8 <productname>ddns
</productname>
12 <contrib>Developer
</contrib>
13 <firstname>Stefan
</firstname>
14 <surname>Schantl
</surname>
15 <email>stefan.schantl@ipfire.org
</email>
21 <refentrytitle>ddns.conf
</refentrytitle>
22 <manvolnum>5</manvolnum>
26 <refname>ddns.conf
</refname>
27 <refpurpose>Configuration file for the DDNS update client.
</refpurpose>
31 <title>Description
</title>
34 The
<filename>ddns.conf
</filename> file is the main configuration file for the
35 <command>ddns
</command> update client. This file specifies some basic options
36 for the programm and contain multiple sections which imply hostname and auth information
37 for each used provider.
41 Lines starting with a hash mark (''#'') and empty lines are ignored.
46 <title>Options
</title>
49 The following options can be configured:
55 <option>proxy = http://IP:PORT
</option>
60 Using this option allows the usage of a proxy server while
65 The proxy only can be contacted by using the HTTP protocol. The
66 server has to be specified by using its IP address and the used port.
70 Example: proxy = http://
192.168.180.1:
800
77 <option>guess_external_ip = [
<emphasis>true
</emphasis>|false]
</option>
82 Determine the public IP addresses by using external servers.
86 The default value if this setting is not configured is
87 <emphasis>true
</emphasis>.
95 <title>Provider Configuration
</title>
98 The DDNS client supports the configuration of an unlimited amount of entries on different providers.
99 Each entry has to be configured as an own section which has to be initiated with the choosen FQDN
100 (Fully Qualified Domain Name) inside of squared brackets.
106 <command>[hostname.someprovider.com]
</command>
111 Specifies the choosen FQDN composed of the hostname and the selected domain from the
112 desired dynamic DNS provider.
119 <command>handle = someprovider.com
</command>
124 The provider which is responsible for the configured FQDN.
128 A list of all supported providers can be found in the
<filename>ddns.conf.sample
</filename>
129 or the
<filename>README
</filename> file shipped by the source code.
136 <command>username = user
</command>
141 The used username to authenticate against your providers update service.
145 In most cases this will be the same username which can be used to login on
146 your providers webpage.
153 <command>password = pass
</command>
158 The choosen password for the specified username.
165 <command>token = token
</command>
170 Just the authentication token.
174 If your dynamic DNS provider supports token-based auth, this method should
183 <title>Examples
</title>
186 <title>A provider which uses username and password for client authentication.
</title>
189 <member>[somehost.provider.com]
</member>
190 <member>handle = provider.com
</member>
191 <member>username = username
</member>
192 <member>password = password
</member>
197 <title>Provider which supports token based auth.
</title>
200 <member>[anotherhost.provider.com]
</member>
201 <member>handle = provider.com
</member>
202 <member>token = token
</member>
211 Please report all bugs to the official bugtracker at
212 http://bugs.ipfire.org/.
217 <title>See Also
</title>
221 <refentrytitle>ddns
</refentrytitle>
222 <manvolnum>1</manvolnum>
225 <refentrytitle>ddns-devel
</refentrytitle>
226 <manvolnum>7</manvolnum>