Changes

Jump to navigation Jump to search
2,250 bytes removed ,  15:58, 18 December 2023
Line 3: Line 3:  
==Version==
 
==Version==
 
{{#smeversion:smeserver-ddclient}}
 
{{#smeversion:smeserver-ddclient}}
  −
<br>
  −
<br>
  −
<br>
  −
<br>
      
== ddclient - DNS record updating ==
 
== ddclient - DNS record updating ==
Line 23: Line 18:  
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]]
 
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]]
   −
This contrib is the official and maintained version for SME Server 8, some Free or paid services of dynamic dns had been incorporated to the contribs.  
+
and for SME10 [mailto:brianr@koozali.org Brian Read] AKA [[User:brianr|brianr]]
====Installation====
  −
* For SME8
  −
You have to enable the [[stephdl]] and [[epel]] repositories.
     −
yum install --enablerepo=stephdl,epel smeserver-ddclient
+
This contrib is the official and maintained version for SME Server 8,9 and 10. Note that some free and paid dynamic dns services have been incorporated into the contrib.
signal-event ddclient
  −
or
  −
  signal-event post-upgrade; signal-event reboot
      +
Also note that ddclient is maintained on github [https://github.com/ddclient/ddclient here] and the full help manual page is [https://wiki.koozali.org/Ddclient-help here].
   −
* For SME9
+
====Installation====
{{Note box|msg=The new version is now in smecontribs,see [[bugzilla: 8338]]}}
+
<tabs container><tab name="For SME 10">
You have to enable the [[stephdl]] and [[epel]] repositories.
+
  yum install --enablerepo=smecontribs smeserver-ddclient ddclient
  yum install --enablerepo=stephdl,epel smeserver-ddclient
      +
</tab>
 +
<tab name="For SME 9 and before">
 +
yum install --enablerepo=smecontribs smeserver-ddclient
 
then  
 
then  
 
  signal-event ddclient
 
  signal-event ddclient
Line 44: Line 36:  
  signal-event post-upgrade; signal-event reboot
 
  signal-event post-upgrade; signal-event reboot
   −
A new panel will be added to the server manager.
+
</tab>
 +
</tabs>
   −
Use this panel to configure domain records you wish to keep updated with your dynamic IP using the ddclient contrib
     −
====How to use====
  −
First you need to create a domain in the server-manager (domains panel) which must match the domain you set with your dynamic dns provider.<br />
     −
For example if the domain you made at DTdns is :
+
There are panels for both the original Server manager (SM1), and the new Server Manager (SM2)
home.dtdns.net
  −
You have to create a relevant domain with this name.
     −
Then go to the panel of "Dynamic clients", choose the domain you made then set your dynamic DNS provider eg (dtdns) and associated credentials to that provider.
+
Use these panels to configure domain records you wish to keep updated with your dynamic IP using the ddclient contrib
   −
====DB settings====
+
{{Note box| As of Dec 2023 The original panel has not been updated to the latest options for ddclient, but the Server manager 2 panel has, see https://wiki.koozali.org/Server_Manager2 to install SM2. However the SM1 panel does work with the latest ddclient, but not all options are presented.}}
   −
*There are some of the services that you can use to detect your external ip
+
====How to use====
 +
First you need to create a domain in the server-manager (domains panel) which must match the domain you set with your dynamic dns provider.<br />
   −
:* ip.changeip.com
+
For example if the domain you made was:  
:* ipdetect.dnspark.com
+
bjrtest.ddns.net
:* checkip.dyndns.org:8245
+
You have to create a relevant domain with this name.
:* checkip.dyndns.org
     −
If you want to change the service which verifies your external ip you can do :
+
Then go to the panel of "Dynamic clients", choose the domain you made then set your dynamic DNS provider and associated credentials to that provider.
   −
config setprop ddclient urlcheckip ip.changeip.com
+
Alternatively you can use the "Custom" are on the Dynamic Clients panel to set the contrib up to update a dynamic DNS entry directly with out needing to have setup a domain.
signal-event ddclient
     −
* Every 300s the contrib perform a check to verify if your ip has been changed to http://checkip.dyndns.org/. you can change the interval of the deamon update by a db command (by default it is 300 seconds). It seems that the minimum accepted is 60s. Possibly you could be blacklisted by providers if you decrease the time-out under of 300s.
+
====DB settings====
 
+
[[File:Screenshot from 2023-12-17 12-02-50.png|alt=|thumb|600x600px|Initial Panel|none]]
config setprop ddclient DeamonUpdate 60
+
[[File:Screenshot from 2023-12-17 12-26-20.png|Modify domain parameters panel|alt=|thumb|600x600px|none]]
signal-event ddclient
     −
* use SSL
+
Here is the
since ddclient 3.7.0 you can encrypt transactions to avoid clear messages. by default forced to yes
     −
config setprop ddclient SSL yes
+
equivalent DB entries for the screens:<syntaxhighlight lang="shell">
or
+
[root@sme10 ~]# db configuration show ddclient
config setprop ddclient SSL no
+
ddclient=service
then
+
     DeamonUpdate=360
signal-event ddclient
+
    Extinterface=eth1
 
+
    ForceIP=
* full db ddclient
  −
# config show ddclient
  −
ddclient=service
  −
     DeamonUpdate=300
   
     SSL=yes
 
     SSL=yes
 +
    cmd=
 +
    debug=disabled
 +
    fwlogin=
 +
    fwpassword=
 +
    method=web
 +
    quiet=enabled
 
     status=enabled
 
     status=enabled
     urlcheckip=checkip.dyndns.org
+
    syslog=enabled
 +
     urlcheckip=googledomains
 +
    verbose=disabled
 +
[root@sme10 ~]#
   −
====Providers available====
  −
Here the official [http://sourceforge.net/p/ddclient/wiki/protocols/ wiki]
  −
  −
* Dyndns.org
  −
* ZoneEdit.com
  −
* Easydns.com
  −
* Hammernode (hn.org)
  −
* dslreports.com
  −
* eurodyndns.org
  −
* Dtdns.com
  −
* loopia.se
  −
* dnspark.com
  −
* Dynhost (ovh.com)
  −
* Noip.com
  −
* Changeip.com
  −
* Namecheap
  −
If your dynamic dns provider is not available in smeserver-ddclient, please raise {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-ddclient|title=a bug }}and provide the  settings for your provider with ddclient (search for settings with google).
      +
</syntaxhighlight>if you change any of these parameters, then you must run the update event as follows:<syntaxhighlight>
 +
signal-event smeserver-ddclient-update
 +
</syntaxhighlight>
 
====Removal====
 
====Removal====
 
+
  yum remove smeserver-ddclient ddclient
  yum remove smeserver-ddclient
   
  signal-event post-upgrade; signal-event reboot
 
  signal-event post-upgrade; signal-event reboot
    
====Debug====
 
====Debug====
* You can keep an eye on log
+
{{Note box|Even with the lower value acceptable (60s) it needs between 60 to 180s to see change in dns record.}}
 +
 
 +
You can keep an eye on log
 
  watch 'cat /var/log/messages|grep SUCCESS'
 
  watch 'cat /var/log/messages|grep SUCCESS'
   Line 127: Line 104:  
and look about hosts in '''NS''' columns.
 
and look about hosts in '''NS''' columns.
   −
* If stuff goes bad you can debug and see what is happening to the deamon
+
* If stuff goes bad you can debug and see what is happening to the daemon
  ddclient -daemon=0 -debug -verbose -noquiet
+
db configuration setprop debug enabled;
 +
db configuration setprop verbose enabled;
 +
  db configuration quiet disabled;
 +
signal-event smeserver-ddclient-update
 
and report please
 
and report please
 +
 +
* keep an eye on the ddclient cache
 +
less /var/cache/ddclient/ddclient.cache
    
==== Bugs ====
 
==== Bugs ====
 
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla] and select the smeserver-ddclient component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-ddclient|title=this link}}.
 
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla] and select the smeserver-ddclient component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-ddclient|title=this link}}.
   −
===smeserver.free.fr version===
+
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-ddclient |noresultsmessage="No open bugs found."}}
 
+
===Changelog===
{{Note box|This contribs is no longer maintained and may be unstable or broke your system}}
+
Only released version in smecontrib are listed here.
{{Warning box|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.}}
  −
 
  −
'''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."
+
{{ #smechangelog: smeserver-ddclient }}
     

Navigation menu