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>
19 <contrib>Developer
</contrib>
20 <firstname>Michael
</firstname>
21 <surname>Tremer
</surname>
22 <email>michael.tremer@ipfire.org
</email>
28 <refentrytitle>ddns.conf
</refentrytitle>
29 <manvolnum>5</manvolnum>
33 <refname>ddns.conf
</refname>
34 <refpurpose>Configuration file for the DDNS update client
</refpurpose>
38 <title>Description
</title>
41 The
<filename>ddns.conf
</filename> file is the main configuration file of the
42 <command>ddns
</command> update client.
43 This file specifies runtime configuration parameters for the programm and
44 contains configurations for dynamic host entries that are managed by
45 <command>ddns
</command>.
49 The syntax of the configuration file is based on the INI configuration
50 file format. Lines starting with hash (#) or semi-colon (;)
56 <title>Options
</title>
59 The following options can be configured:
65 <option>proxy = http://IP:PORT
</option>
70 This option will configure the HTTP proxy server that is used to
71 communicate with the providers HTTP APIs.
75 The proxy only can be contacted by using the HTTP protocol. The
76 server has to be specified by using its IP address and port.
77 For example:
<option>proxy = http://
192.168.180.1:
800</option>
84 <option>guess_external_ip = [true|
<emphasis>false
</emphasis>]
</option>
89 Determine the public IP addresses by using external servers.
93 By default, this option is disabled and automatically enabled
94 if the client has only IP addresses defined in RFC1918 or
95 other reserved address space.
103 <title>Provider Configuration
</title>
106 The DDNS client supports the configuration of an unlimited amount of entries for different providers.
107 Each entry has to be configured as an own section named by the FQDN (Fully Qualified Domain Name)
108 inside squared brackets.
114 <command>[hostname.someprovider.com]
</command>
119 The FQDN of the dynamic host. This name will be resolved
120 by
<command>ddns
</command> and therfore must not be a handle or something
128 <command>handle = someprovider.com
</command>
133 The provider which is responsible for this host.
137 A list of all supported providers can be looked up by running
138 <command>ddns list-providers
</command>.
145 <command>username = user
</command>
150 The username to authenticate against the provider's update service.
154 In most cases this will be the same username which can be used to login on
155 your provider's web page.
162 <command>password = password
</command>
167 The choosen password for the specified username.
174 <command>token = token
</command>
179 An authentication token.
183 If your dynamic DNS provider supports token-based authentication,
184 this method should be prefered.
185 You do not need to specify the username if token-based authentication
194 <title>Examples
</title>
197 <title>For providers which use username and password for client authentication
</title>
200 <member>[somehost.provider.com]
</member>
201 <member>handle = provider.com
</member>
202 <member>username = username
</member>
203 <member>password = password
</member>
208 <title>For providers which supports token-based authentication
</title>
211 <member>[anotherhost.provider.com]
</member>
212 <member>handle = provider.com
</member>
213 <member>token = token
</member>
222 Please report all bugs to the official bugtracker at
223 http://bugs.ipfire.org/.
228 <title>See Also
</title>
232 <refentrytitle>ddns
</refentrytitle>
233 <manvolnum>1</manvolnum>