JustASRV

pfSense

Applies to pfSense CE 2.6+ and pfSense Plus. pfSense's Custom Dynamic DNS type sends an HTTPS request with HTTP Basic authentication, which is what JustASRV expects.

Configure

  1. Go to Services › Dynamic DNS › Dynamic DNS Clients and click Add.
  2. Service Type: Custom
  3. Interface to monitor: the WAN that the hostname should follow.
  4. Interface to send update from: the same WAN.
  5. Verify SSL/TLS Certificate Trust: leave checked.
  6. Username: acme-main.ddns.justasrv.com
  7. Password: the jas_… token.
  8. Update URL:
    https://ddns.justasrv.com/nic/update?hostname=acme-main.ddns.justasrv.com&myip=%IP%
  9. Result Match: good %IP%|nochg %IP%
  10. Max Cache Age: 1 (forces a refresh at least daily, so JustASRV can tell the firewall is alive).
  11. If the WAN interface itself has a private address (the pfSense sits behind another router), tick Use Public IP if your version shows it, so that %IP% is the public address and the Result Match succeeds.
  12. Save, then click Save & Force Update.

The cached IP on the Dynamic DNS Clients list turns green on success. Details are under Status › System Logs › System › General (filter on dyndns).

Status thresholds

With Max Cache Age 1, pfSense reports at least once a day and on every WAN change. On the hostname in the portal set Stale after = 1560 minutes (26 h) and Offline after = 3000 minutes (50 h).

Notes

  • Result Match is compared with the whole response, with %IP% replaced by the address pfSense detected. JustASRV answers with the address it actually published; a mismatch means pfSense and JustASRV see different addresses (usually double NAT). The DNS record is still correct: check the hostname's history in the portal.
  • For multi-WAN, create one hostname and one client per WAN.