Dynamic DNS stopped updating

[Monviech (Cedrik)]

Well yes please read my earlier post.

[franco]

We isolated the cause and discussing possible fixes. At the moment virtual fields such as the current_* fields in models are ignored by the grid rendering which was not intended.


Cheers,
Franco

[franco]

# opnsense-patch https://github.com/opnsense/core/commit/61d289cb3f

[staticznld]

Looks like that is working!

Thanks.

[Javier®]

Hi, it works for me. Thanks.

[sammy]

thanks, the patch works!

[akyfire]

Brilliant, it's fixed two site's with the issue for me

[Meg]

The patch works great. Thanks.

[rfox]

Patch works great! But I noticed that when configured through the GUI - it doesn't work (using DynDNS) - have to configure the /usr/local/etc/ddclient.conf by hand - when using the GUI, it resets the manually made ddclient.conf and doesn't respect the settings made ?!?

Manually created - which works fine:
root@FoxOPN:/usr/local/etc # cat ddclient.conf
daemon=300
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.
ssl=yes

usev4=ifv4, ifv4=vtnet1, \
protocol=dyndns2, \
login=(redacted), \
password=(redacted)\
xxxx.homeip.net

After hitting "apply" in the GUI:

root@FoxOPN:/usr/local/etc # cat ddclient.conf
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.

[franco]

> when using the GUI, it resets the manually made ddclient.conf and doesn't respect the settings made ?!?

That's intentional.  You could always use ddclient without the plugin, but then also without a widget and other hooks into the system.

The middle ground is get your missing features into the plugin.


Cheers,
Franco

[rfox]

> when using the GUI, it resets the manually made ddclient.conf and doesn't respect the settings made ?!?

That's intentional.  You could always use ddclient without the plugin, but then also without a widget and other hooks into the system.

The middle ground is get your missing features into the plugin.


Cheers,
Franco

Thx Franco - I know it's intentional that the ddclient.conf file is overwritten from the GUI plugin - but don't think it's intentional that the GUI does not respect the settings made and NOT put them into the ddclient.conf - I have one entry under accounts - filled out correctly, but when I hit apply, it saves and overwrites the ddclient.conf file with only those two entries found above ?!?  So hitting apply breaks the config . . .

[Monviech (Cedrik)]

That is to be expected since each apply will generate the complete configuration file with the information found in the config.xml.

[rfox]

That is to be expected since each apply will generate the complete configuration file with the information found in the config.xml.

Huh? Maybe I'm not explaining this correctly.  If I use the GUI under Dynamic DNS to create a DynDNS account configuration using native backend - and save it using apply, it doesn't work.  When I look at the resulting ddclient.conf I see only:

root@FoxOPN:/usr/local/etc # cat ddclient.conf
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.

Which doesn't show the items I placed in the GUI under accounts like login, password, ssl, etc.

Is the ddclient.conf being generated on the fly together with the config.xml settings?  I don't get it . . .

[franco]

The native backend doesn't use ddclient.conf nor ddclient itself. Look at /usr/local/etc/ddclient.json instead.

I know it's confusing. Maybe one day we will even remove the ddclient backend or split the plugins into two.


Cheers,
Franco

[rfox]

The native backend doesn't use ddclient.conf nor ddclient itself. Look at /usr/local/etc/ddclient.json instead.

I know it's confusing. Maybe one day we will even remove the ddclient backend or split the plugins into two.


Cheers,
Franco

Gotcha !  So when I choose "native" backend - it clears out the ddclient.conf - and doesn't work.

When I change backend back to ddclient - it seems to keep my ddclient.conf after hitting apply. Only thing is, I don't see it updating automatically (respecting the 300 second default interval) . . . shouldn't I see an update attempt every 5 minutes in the ddclient logs ??