UniFi Cloudflare DDNS
Hi there!
Recently, we received an update from UniFi that allows us to use Cloudflare DDNS to modify the IP address of our domain DNS records. I’ve tested it, and it seems to be working.
However, there’s an issue with the proxy status on Cloudflare for that DNS record. It doesn’t seem to be carrying over from the original “proxied?” status. Does anyone know if there’s a fix for this or if there are any plans to address it?
For instance, I have two DNS-only records and one proxied record. When the update was applied, the proxied record was mistakenly set to DNS-only.
I’d greatly appreciate any help or insights you can provide on this matter.
7 Replies
That seems like an issue with how UniFi implemented the DDNS. It would need to be fixed on their end
I see, thank you
I talked to support and they said they would share the feedback with the team
It could be by design. Just thinking about this. You use DDNS to return your IP address. If it's a proxy record, it obviously won't return your IP through the DDNS update? But interesting either way. 🙂
UniFi is acting as my router in this case, so it always knows the current IP assigned by my ISP since it’s directly connected via the WAN. It uses the Cloudflare API credentials to update the IP address of the configured DNS records—only if it detects a change—so the initial state of the record (including whether it’s proxied or not) doesn’t really matter from an update perspective.
That said, I do agree it’s strange that the proxied status isn’t preserved. I know a server-side script could achieve the same thing, but having this built directly into the router is just so much more convenient.
With a script, you can explicitly control the proxy flag via the API. But I’m not sure how UniFi is handling that part under the hood—maybe they just don’t send that parameter at all, or they default to DNS-only.
🙂 Interesting one for sure
Not ideal, but one why you can work around it is to have UniFi have an obscure DDNS record. Something like 6b149efd4dc00750216779359957a769.yourdomain.com, then have a proxied CNAME record pointing to that. Like unifi.yourdomain.com CNAMEd 6b149efd4dc00750216779359957a769.yourdomain.com.
That actually doesn’t seem like a bad idea at all! Thank you 🙂