Difference between revisions of "Ddclient"

From SME Server
Jump to navigationJump to search
Line 1: Line 1:
{{#smeversion:smeserver-ddclient}}
 
  
 
== ddclient - DNS record updating ==
 
== ddclient - DNS record updating ==
 +
{{#smeversion:smeserver-ddclient}}
  
 
Use this contrib when you have a sme server connected to a ISP service using a dynamic IP, and you wish to host multiple domains.  
 
Use this contrib when you have a sme server connected to a ISP service using a dynamic IP, and you wish to host multiple domains.  

Revision as of 04:35, 8 May 2013

ddclient - DNS record updating

Contrib 10:
Contrib 9:
smeserver-ddclient
The latest version of smeserver-ddclient is available in the SME repository, click on the version number(s) for more information.


Use this contrib when you have a sme server connected to a ISP service using a dynamic IP, and you wish to host multiple domains.

ddclient is a client for updating dynamic DNS entries for domains hosted at different DNS providers.

Configure your dynamic host domains via the ddclient server manager panel.

ddclient can be used on servers configured in server gateway mode or in server only mode.


Warning.png Warning:
When you have the smeserver.free.fr sme7-ddclient contrib installed and you run yum upgrade with the smecontribs repository enabled on your server, watch out! There is a smeserver-ddclient package that will get installed as an upgrade and this conflicts with the sme7-ddclient package ! Remove the sme7-ddclient first, see instructions below.



SME contribs repo version

Note: There appears to be a number of unresolved problems with the smeserver-ddclient contrib which prevent proper functionality.

For details of these problems, refer to http://bugs.contribs.org/buglist.cgi?quicksearch=smeserver-ddclient&list_id=11233 (at December 2012)

User are advised to install the sme7-ddclient contrib referred to below, which is known to work on SME 8.

Installation

yum install --enablerepo=smecontribs smeserver-ddclient

There is no need to run the signal-event post-upgrade and reboot commands.

A new panel will be added to the server manager.

Use this panel to configure domain records you wish to keep updated with your dynamic IP using the ddclient contrib

Removal

yum remove smeserver-ddclient

smeserver.free.fr version

Note: This RPM works with SME 8 or SME 7

The smeserver.free.fr site appears to be defunct (since at least April 2012), so this article provides a link to the contrib at another external file download site.

This contrib has some additional features like the ability to select the method on how the detect the external IP address and the ability to publish arbitrary domain names (i.e. not just the ones that are on your server).

Installation

Download the latest rpm version from

http://www.files.com/shared/4f89e32b9c187/sme7-ddclient-3.7.3-7.noarch.zip

to an empty folder eg /tmp and unzip the file

unzip sme7-ddclient*

The currently available rpm is:

sme7-ddclient-3.7.3-7.noarch.rpm

Then cd to that folder and install the rpm (change the rpm name in the following command to match the latest available version)

cd /tmp
yum localinstall sme7-ddclient*.rpm

Removal

yum remove sme7-ddclient
signal-event post-upgrade;signal-event reboot

Using SME default dynamic client & external DNS CNAME entries

In many cases, you really do not need to use ddclient or some variation of it eg sme7-ddclient or smeserver-ddclient

You can use the built in dynamic client for your main domain (accessible by running Configure this server from the admin console).

Then create CNAME entries in external DNS records which point at the main domain name.

SME will update the main domain name/dynamicIP change, and the additional domains will follow it as the external IP changes.

The use of this method is only possible where the full DNS records are accessible & editable by admin users.

In some situations with DNS service providers, these DNS records are not accessible, in that case you will need to use one of the ddclient methods.

Also see http://bugs.contribs.org/show_bug.cgi?id=6206#c9 which says:

"I notice that you mention two dyndns domains, but you should be able to set up domain2.x.y to be a CNAME for domain1.x.y, then configure domain1.x.y with the builtin client."