JustASRV

Router compatibility

JustASRV speaks the DynDNS v2 (dyndns2) update protocol over HTTPS, the de-facto standard that most firewalls and DDNS clients implement for "custom" providers. If a device supports a custom dyndns2 server with a username and password, it works with JustASRV.

Values for any dyndns2 client

ProtocolDynDNS v2 / dyndns2, HTTPS
Serverddns.justasrv.com
Path/nic/update
Usernamethe full hostname, e.g. acme-main.ddns.justasrv.com
Passwordthe token (jas_…)
Hostnamethe full hostname
Check-IP URLhttps://ddns.justasrv.com/ip (plain-text answer)

Compatibility summary

PlatformNative supportHeartbeatGuide
pfSense (CE / Plus)Yes: Custom providerNo (updates on change + daily with Max Cache Age 1)pfSense
OPNsenseYes: os-ddclient, dyndns2No (updates on change)OPNsense
MikroTik RouterOS 6.43+ / 7Yes: scheduled scriptYesMikroTik
OpenWrt (ddns-scripts)Yes: custom update URLYes (force interval)OpenWrt
UniFi (UniFi OS gateways)Partial: see guideNoUniFi
Fortinet, SonicWall, consumer routersVaries / often non/aOther devices
ddclient, inadynYes: dyndns2ConfigurableOther devices
Windows / Linux machine at the siteJustASRV updaterYes (every 10 min)Windows · Linux

Heartbeat vs. change-only

Some clients report only when the address changes. That is fine for DNS, but JustASRV cannot tell a quiet site from a dead one. For those hosts, an administrator sets longer status thresholds on the hostname (Host → Settings), or adds a heartbeat updater at the site. Each guide gives recommended values.

Addresses and NAT

By default JustASRV publishes the address the update request came from and ignores a myip= value that differs. This is correct for almost every site and cannot be spoofed. If an updater's traffic leaves through a different connection than the one the hostname should point to (for example, a dual-WAN site with a policy route), an administrator can switch that host to "accept public myip=". Private, loopback, CGNAT (100.64.0.0/10) and reserved addresses are always refused.

If the site is behind carrier-grade NAT (common on Starlink, some LTE and fixed-wireless ISPs), inbound connections to the public address do not reach the site at all. DDNS will publish the carrier's address correctly, but VPN or port-forward traffic to it will not arrive. That is an ISP limitation, not a DDNS one.