ClearFoundation

Ben Chambers wrote:
Have you installed the ClearCenter Dynamic DNS app from the Marketplace? It is not installed by default.

B.

Yes, I have. I can update my IP manually from my ClearOS console and from the Clearcenter Portal.

Marcel van Leeuwen wrote:
Have you opened port TCP 1875 (Service ClearSDN)? Network --> Incoming Firewall --> Allowed Incoming Connections --> Add --> Standard service --> select ClearSDN and add.

Thanks for this suggestion.
As I didn't know what this was for, I had removed it.

I've added it again now, but still no luck. I suppose this port also has to be opened on my router?

owh, you don't use ClearOS as a gateway. You have to open this port on your firewall you use.

Marcel van Leeuwen wrote:
owh, you don't use ClearOS as a gateway. You have to open this port on your firewall you use.

I do! But I use my ISP box as the public network, and only have my ClearOS behind for my own private network.

Added the port to the firewall, will refresh my IP to check if it works.

Actually, dynamic DNS isn't one of the ClearSDN services that requires 1875.

To the OP...I would suggest running the script


To see what the result is...there may be some hints in your log files.

B

Ben Chambers wrote:
Actually, dynamic DNS isn't one of the ClearSDN services that requires 1875.


Hmm, i thought you also needed to open port 1875 for the DNS service. I apologize for giving the wrong information.

If memory serves, the only current-day services that require 1875 open are remote security audit, remote backup server and resource monitor (bandwidth monitor has been dropped until it can be re-written with some more useful information/data).

B

I tried the dnsupdate command (without force) and it worked!
No errors, no issues...

Also I was so fed up, I did a complete reinstall of the system, but the issue is still there.
It's quite annoying as my IP changes every 4 days. Then my DNS-name is 'down' and I have to manually change the IP.

I did see when performing a restart of the system (and the IP has changed), it will also automatically update the IP.
It's as if the dnsupdate works, but the job doesn't run or isn't scheduled?

It is not the right answer, but you can add a line "dnsupdate" to the end of /etc/dhclient-exit-hooks which should fire every time your lease renews. You may need the full path to it "/usr/sbin/dnsupdate".

Somewhere the syswatch service should be looking after this. Is it running?

Nicks right about the syswatch daemon handling the triggering of dnsupdate script.

Why don't you add some logging, by logging into the server as root and typing:


Then posting up some of your /var/log/syswatch log file after you go through a known IP event (eg. you can force it by cycling power on your DSL modem).

Ben