WireGuard Endpoint DNS Resolution Fails After DDNS IP Changes on pfSense 2.8.1

[assaeed]

Hi everyone,

I am facing a persistent issue with WireGuard on pfSense 2.8.1 regarding Endpoint DNS resolution.

My Setup:

pfSense Version: 2.8.1 (Latest)

DDNS Provider: Paid No-IP service.

Configuration: The WireGuard Peer is configured using the DDNS hostname as the Endpoint.

The Problem:
Everything works perfectly for a few days right after the initial setup or a reboot. However, as soon as my ISP changes my dynamic IP and No-IP updates the DDNS record, the WireGuard tunnel goes down and fails to reconnect.

It seems that WireGuard on pfSense does not automatically re-resolve the DDNS hostname once the IP changes. The server completely loses track of the peer's new IP.

What I’ve Tried So Far:

Configured the No-IP DDNS directly on pfSense (updates successfully in the DDNS status, but WireGuard doesn't pick it up).

Moved the DDNS client configuration to the ISP Modem/Router instead, but the exact same behavior occurs.

The only way to restore the connection is to manually restart the WireGuard service or force a re-load of the tunnel.

Is there a built-in mechanism or a recommended cron job/script in pfSense 2.8.1 to force WireGuard to periodically re-resolve Endpoint hostnames? Any help or workarounds to fix this persistent DNS resolution issue would be highly appreciated.

Thank you!

[Bob.Dig]

@assaeed Sadly there is none I am aware of.