[BUG] daemon interval is being ignored

[Jerks88]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi,

here is my ddclient.conf:

daemon=30
syslog=yes
pid=/var/run/ddclient/ddclient.pid

use=web, web=http://checkip.amazonaws.com/
protocol=dyndns2
server=dynv6.com
login=none
password='password'
host=domain.dns.army

When the container starts the ip is registered correctly at dns.army. When I manually delete the record at dns.army it should reappear after 30s, but it doesn't. Even after 30 min it doesn't get registered again, I have to restart the whole container.

Expected Behavior

It should register the IP every 30s at the dyndns endpoint.

Steps To Reproduce

Just deploy your docker container with latest image and use my ddclient.conf.

Environment

- OS: TrueNAS Scale 25.04.1 (Debian 12)
- preinstalled on TrueNAS Scale

CPU architecture

arm64

Docker creation

services:
  ddclient:
    image: lscr.io/linuxserver/ddclient:latest
    container_name: ddclient
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - /mnt/pool-nvme1-data/app-config-storage/ddclient/config:/config
    restart: unless-stopped

Container logs

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID:    1000

User GID:    1000

───────────────────────────────────────

Linuxserver.io version: v4.0.0-ls205

Build-date: 2025-08-05T07:05:14+00:00

───────────────────────────────────────

    

[custom-init] No custom files found, skipping...

Setting up watches.

Watches established.

[ls.io-init] done.

SUCCESS: [dyndns2][domain.dns.army]> IPv4 address set to <My Public IP>

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[aptalca]

We develop and support the container, not the app inside. You should ask them.

But, as far as I know, it will try to set the dns records when the ip changes. It won't check to see if someone deleted or modified the dns records. And it won't try to set them forcefully every 30 seconds.

So a proper test would involve changing the local ip, not modifying the dns record.

I'm pretty sure most dynamic dns updaters assume they have exclusive control over the A record of the domain(s) they're managing.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity