cesy
New Member
Hello,
I’m trying to configure **Dynamic DNS** in OPNsense to automatically update my IP address on **ZoneEdit**, but the update fails when using the built-in ddclient integration.
The log shows the following error:
Here’s my current configuration from `/usr/local/etc/ddclient.json`:
However, when I run **ddclient** manually with this configuration, it works properly and updates the IP:
In the OPNsense interface, the available protocol options are:
`DynDNS 1`, `DynDNS 2`, `Custom GET`, `Custom POST`, and `Custom PUT`.
Since ZoneEdit typically uses the `zoneedit1` protocol, I’m wondering if the issue could be related to this — perhaps OPNsense’s `dyndns1` option generates a URL or request format that ZoneEdit doesn’t recognize, leading to the 404 response.
Could anyone confirm if there’s a way to configure ZoneEdit properly from the UI (for example, using a “Custom GET/POST” option with a manually defined URL)?
Or would this require explicit support for the `zoneedit1` protocol in OPNsense?
Thanks in advance!
*(Note: some values such as domain names, user credentials, and IDs have been modified for security reasons.)*
I’m trying to configure **Dynamic DNS** in OPNsense to automatically update my IP address on **ZoneEdit**, but the update fails when using the built-in ddclient integration.
The log shows the following error:
Code:
2025-10-25T18:01:11 Error ddclient Account xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [custom - DDNS ZoneEdit] failed to set new ip xx.xxx.xxx.xxx [404 - <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL was not found on this server.</p></body></html>]Here’s my current configuration from `/usr/local/etc/ddclient.json`:
JSON:
{
"general": {
"enabled": true,
"verbose": false,
"allowipv6": false,
"daemon_delay": 300
},
"accounts": [
{
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"service": "custom",
"protocol": "dyndns1",
"server": "dynamic.zoneedit.com",
"resourceId": "",
"username": "my-user",
"password": "my-token",
"hostnames": "my-domain.com,*.my-wildcard-domain.com",
"wildcard": false,
"zone": "",
"checkip": "web_zoneedit",
"interface": "pppoe0",
"dynipv6host": "",
"checkip_timeout": 10,
"force_ssl": false,
"ttl": "300",
"description": "DDNS ZoneEdit"
}
]
}However, when I run **ddclient** manually with this configuration, it works properly and updates the IP:
Code:
server=dynamic.zoneedit.com,
use=if, if=pppoe0,
protocol=zoneedit1,
login=my-user,
password=my-token
my-domain.com,*.my-wildcard-domain.comIn the OPNsense interface, the available protocol options are:
`DynDNS 1`, `DynDNS 2`, `Custom GET`, `Custom POST`, and `Custom PUT`.
Since ZoneEdit typically uses the `zoneedit1` protocol, I’m wondering if the issue could be related to this — perhaps OPNsense’s `dyndns1` option generates a URL or request format that ZoneEdit doesn’t recognize, leading to the 404 response.
Could anyone confirm if there’s a way to configure ZoneEdit properly from the UI (for example, using a “Custom GET/POST” option with a manually defined URL)?
Or would this require explicit support for the `zoneedit1` protocol in OPNsense?
Thanks in advance!
*(Note: some values such as domain names, user credentials, and IDs have been modified for security reasons.)*
