Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: sonoracomm on January 09, 2007, 10:00:15 PM
-
Hi Folks,
We usually use static IP addresses for our customer networks, so I have rarely dealt with DDNS on SME Servers.
I just had to revisit the subject (for my home server), so I created a quickie howto.
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=132&Itemid=32
I hope this helps someone...
G
Edited:
I changed the installation command as suggested below as it's better and easier. (what ELSE is in that smedev repo?!)
This method of using dynamic DNS has a couple of really major advantages over the built-in dyn-DNS feature:
1) it works in server-only or server-gateway mode
2) you can have your SME 7 domain be different than the dynamic DNS domain
-
Hi sonoracomm,
Is this for server/gateway and server only modes. Am I right in assuming that it allows for more than one domain per server? I have used the built in one for 5 years in server/gateway mode with no problems, but it only works for the main domain.
Del
-
Can you install with...
yum --enablerepo=smedev install sme7-ddclient
-
Hello,
The built-in dynamic DNS feature of SME 7 is useless for users of free DDNS services.
Hm? Did I miss anything? I'm for sure working with the free DynDNS service of dyndns.org and SME 7.1, and it's working! Untill you don't want a bunch of dynamic addresses pointing to your server, the built-in DynDNS update script is enough for you.
The only problem, including one workaround plus one suggestion for the bugfix, is described in my bugreport 2314 (http://bugs.contribs.org/show_bug.cgi?id=2314)
So for most people there is no need to install the ddclient, hence the howto is futile for them.
Greetings, Mirko
-
The built-in dynamic DNS feature of SME 7 is useless for users of free DDNS services.
Hm? Did I miss anything? I'm for sure working with the free DynDNS service of dyndns.org and SME 7.1, and it's working! Untill you don't want a bunch of dynamic addresses pointing to your server, the built-in DynDNS update script is enough for you.
There is never any real need for multiple dynamic addresses. One can be dynamic, and the others can be CNAME records referring to the dynamic address.
-
One can be dynamic, and the others can be CNAME records referring to the dynamic address.
mail.domain.com cannot be a cname it has to point to an arecord (IP address) on ZoneEdit.com
but this is a great idea
-
One can be dynamic, and the others can be CNAME records referring to the dynamic address.
mail.domain.com cannot be a cname it has to point to an arecord (IP address) on ZoneEdit.com
but this is a great idea
With dyndns.com it can.
A Record domain.com >> 1.2.3.4
CNAME mail.domain.com >> domain.com
-
One can be dynamic, and the others can be CNAME records referring to the dynamic address.
mail.domain.com cannot be a cname it has to point to an arecord (IP address) on ZoneEdit.com
but this is a great idea
With dyndns.com it can.
A Record domain.com >> 1.2.3.4
CNAME mail.domain.com >> domain.com
mail.domain.com can be a CNAME, but then mail.domain.com cannot be listed as the MX for domain.com. I think this is what the original poster was intending to say.
-
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=87&Itemid=32
-
I have just installed sme7-ddclient and all went well.
yum --enablerepo=smedev install sme7-ddclient
thanks for that tid bit
When I try to configure the ddclient tab what is the bottom line for? "Record MX"
Is this where I should put mail.domain.com?
-
WARNING: caught SIGTERM; exiting
I get this error in an email from anonymous@domain.com
-
WARNING: caught SIGTERM; exiting
I get this error in an email from anonymous@domain.com
Have seen this more times than I care to remember on server running DynDNS... Nothing to worry about I reckon, if it's not broken, don't try and fix it...
Have never lost connection to the server, so I reckon nothing to worry about
-
does is matter if I use zoneedit or is this just a general error.
I don't think that I have seen it today or yesterday. I did just upgrade my system to 7.1 in the mean time. Maybe that fixed it.
just don't know
-
This has nothing to do with zoneedit or any other dns provider.
This has something to do with the server. And if the problem returns post a bug ticket.
-
It is a known issue and already n the bug tracker.
http://bugs.contribs.org/show_bug.cgi?id=2057#c7
If ddclient is re-started for any reason (even a normal reboot), it sends that annoying email.