CLI does not re-register linked IP when ISP changes public IP silently

Subject: CLI does not re-register linked IP when ISP changes public IP silently

Hi NextDNS team,

I'm using the NextDNS CLI (v1.47.2) on an ASUS GT-AX6000 router running AsusWRT-Merlin firmware. My ISP is DIGI (Spain) and I have a dynamic public IP.

The problem:
When I restart the router, the CLI registers the new IP correctly and everything works. However, when the ISP changes my public IP silently (without any WAN disconnection/reconnection), the CLI keeps running but does not re-register the new IP with NextDNS servers. As a result, the linked IP in my NextDNS profile becomes outdated and DNS filtering stops working for all devices on my network.

Setup details:
- Device: ASUS GT-AX6000
- Firmware: AsusWRT-Merlin 3006.102.7_2
- NextDNS CLI version: 1.47.2
- ISP: DIGI Spain (dynamic IP)
- Config: listen localhost:53, setup-router true, report-client-info true

What I have tried:
- nextdns restart — does not re-register the IP
- nextdns stop + start — does not re-register the IP reliably
- nextdns set — shows the help menu, unclear if it works
- A cron job every 10 minutes using nvram get wan0_ipaddr to detect IP changes and restart the CLI
- Forcing DDNS update with service restart_ddns so NextDNS can resolve the updated domain

The core issue seems to be that when the ISP changes the IP without a WAN reconnection event, the CLI has no mechanism to detect this and re-register the new IP with NextDNS servers.

Is there a reliable command or configuration option to force the CLI to re-register the linked IP? Or is this something that could be addressed in a future release?

Thank you.