Dual Stack he.net Custom POST protocol on OPNsense 23.7.4

[arvendui]

Version 1: 9/17/2023

Because it’s free and after bloodying my forehead for a weekend, this method seems to work flawlessly with he.net's Dynamic DNS Service for my dual stack set up.

This guide describes one approach to utilize the os-ddclient native backend to facilitate updating he.net DDNS on a dual-stack network with the Custom Post protocol option. Thank you to DaCookie4u!

Install os-ddclient plugin (Dynamic DNS)

Configure Services / Dynamic DNS / Accounts (two accounts required, one for each ip stack)

IPv6

• Enabled: checked
• Description: Give it one that denotes IPv6
• Service: custom
• Protocol: Custom POST
• Server: https://dyn.dns.he.net/nic/update
• Username: Corresponding domain name of AAAA Dynamic DNS Record @ he.net
• Password: Corresponding key of AAAA Dynamic DNS Record @ he.net
• Hostname(s): Corresponding domain name of AAAA Dynamic DNS Record @ he.net (ie. Username & Hostname identical)
• Check ip method: Any method that exclusively returns an IPv6 address
• Interface to monitor: WAN
• Force SSL: checked

IPv4

• Create the IPv4 Service just as the IPv6 above, with the following exceptions:
• Description: Give it one that denotes IPv4
• Check ip method: Any method that exclusively returns an IPv4 address

Important: When utilizing he.net's Free DNS Service, Usernames (which is yourdomain.com), Hostnames (also yourdomain.com), and Passwords (keys) are identical for both IPv6 & IPv4. When you change either A or AAAA record keys for an identical hostname, you change both record keys. (https://dns.he.net/docs.html)

When you get done with that, you should see something like this, but likely less blurry 

Configure Services / Dynamic DNS / Settings / General Settings

• Enable: checked
• Verbose: Likely a good idea to check it, until you know it works for you
• Allow IPv6: checked
• Interval: default is 300, I later went with 600 (10 minutes)
• Backend: native (important as default is ddclient!)

Nirvana!