[SOLVED] Zentyal DDNS Problems?

[jjm1982]

Does anyone know if there is a DDNS problem with Zentyal and the domain servers. My cable modem experienced a problem yesterday and was down for multiple hours. Once I resolved that issue, it was handed a new IP address. This new IP address is correctly presented in the Zentyal subscription page but when I perform an NSLOOKUP from the command line, my old IP address is resolved. This is preventing all of my remote servers to connect to my servers through VPN.

My server has all the latest updates and Zentyal updates that have been made available.

[majestyx]

once, i had a similar problem

a unsubscribe an a new subscribe to z-cloud was "my personal work around" 

[jjm1982]

I don't believe it should work that way. I've also had problems when I unsubscribe and resubscribe to Zentyal. I would hate to have to work through those issues just to have the IP address translating correctly when I perform a DNS lookup.

I would also hate to have to switch back to one of the free ddns services because I find Zentyal DDNS to be more useful.

[jjm1982]

I found an unlikely solution but it works. Changing the DDNS information from Zentyal to something like DynDNS and entering in fictitious information (only because it will be temporary) then save changes. After the changes have been changed, revert back to Zentyal as being the DDNS option an save changes again. This apparently forces the IP address to be updated in the Zentyal Cloud. You can verify this by looking at the DDNS update log.

Ideally, the IP address should be updated automatically.

[EddieA]

Ideally, the IP address should be updated automatically.

The IP address should be persisted, and every time the external interface is brought up, the current IP should be compared to the persisted one, and if different, the DDNS service notified, and the new IP persisted.

Cheers.

[robb]

I have experienced the same problems and What I do is force the DDclient believe the IP address is a wrong IP address. Then it will update.
Forcing the IP address in ddclient you perfrom the following command:

Code: [Select]

sudo ddclient -use=ip -ip=1.2.3.4 -daemon=0
I don't know if this is the solution, but when I look at the ddclient config file, I found that the 'run-deamon' was set to 'false'

Code: [Select]

# Set to "true" if ddclient should run in daemon mode.
run_daemon="true"
I set it back to true and had no problems anymore with updating the ipaddress

You can find the ddclient configfile at /etc/default/ddclient

[jjm1982]

I have experienced the same problems and What I do is force the DDclient believe the IP address is a wrong IP address. Then it will update.
Forcing the IP address in ddclient you perfrom the following command:

Code: [Select]

sudo ddclient -use=ip -ip=1.2.3.4 -daemon=0
I don't know if this is the solution, but when I look at the ddclient config file, I found that the 'run-deamon' was set to 'false'

Code: [Select]

# Set to "true" if ddclient should run in daemon mode.
run_daemon="true"
I set it back to true and had no problems anymore with updating the ipaddress

You can find the ddclient configfile at /etc/default/ddclient

Thanks for the info! But when I checked the ddclient file the run_daemon was already set to true. Though I will keep the first command in the back of my mind in case I need to do this manually in the future. Perhaps it should be setup in a cron job of some kind?