We are using the ddns feature for network filtering for clients with DHCP addresses. we ran into an issue with defensx not responding to the dns query for api.defensx.me when the IP changed for the WAN interface, this caused the ddns feature built into our firewalls to be unable to inform the ddns that the Ip had changed. Our workaround is to have a dns forwarder in place that uses public DNS for that hostname.