unifi 华为_使用Unifi Dream Machine Pro自定义动态DNS

unifi 华为

I recently bought a UniFi Dream Machine Pro (UDM Pro). I did a ton of research before getting it and saw Dynamic DNS (DDNS) support. But it only supported a hand full of DDNS providers. My domains are in AWS Route53, and I did not want to pay premium pricing for the supported DDNS providers. So I embarked on a journey to create a personal provider to update a subdomain hosted in AWS Route53.

我最近购买了UniFi Dream Machine Pro(UDM Pro)。 在获得它之前，我做了很多研究，并看到了动态DNS(DDNS)支持。 但是它只支持一堆DDNS提供程序。 我的域位于AWS Route53中，我不想为受支持的DDNS提供商支付高价。 因此，我开始了创建个人提供商以更新AWS Route53中托管的子域的旅程。

I first need to figure out how I am going to do it. What does the UDM Pro do? What do the other DDNS providers have that allows the UDM Pro to update them? Any specific configurations I need to set on the UDM Pro?

我首先需要弄清楚我将如何做。 UDM Pro会做什么？ 其他DDNS提供商有哪些可以让UDM Pro更新它们？ 我需要在UDM Pro上设置任何特定的配置吗？

UDM Pro如何通知DDNS提供商？ (How does UDM Pro notify a DDNS Provider?)

To figure this out, I had to go through the logs of my UDM Pro and see what happens when I set up a dummy DDNS Provider. I gave it fake credentials, so it would fail and spit something out to the logs. It turns out that the UDM Pro uses Internet Automated Dynamic DNS Client (Inadyn), which is an Open Source tool!

为了弄清楚这一点，我必须仔细阅读UDM Pro的日志，看看设置虚拟DDNS提供程序时会发生什么。 我给它提供了伪造的凭证，因此它将失败并向日志中吐出一些东西。 事实证明，UDM Pro使用Internet自动动态DNS客户端 (Inadyn)，这是一个开放源代码工具！

Inadyn has excellent documentation and even supports more providers than UniFi OS (the software that UDM Pro runs) allows. But since Route53 is just a DNS provider without a native way to dynamically update records, I would still have to roll out a custom solution. Luckily, Inadyn supported custom configuration, which means I could set up any API I wanted, and I could get Inadyn to communicate with it appropriately!

Inadyn具有出色的文档资料，甚至比UniFi OS(UDM Pro运行的软件)所允许的支持更多的提供商。 但是由于Route53只是一个DNS提供程序，没有本机方式来动态更新记录，因此我仍然必须推出自定义解决方案。 幸运的是，Inadyn支持自定义配置，这意味着我可以设置所需的任何API，而且我可以让Inadyn与其进行适当的通信！

But I know there has to be a standard DDNS API somewhere. I went through some of the supported providers and found that https://dyn.com had some documentation around their APIs (https://help.dyn.com/remote-access-api/). It went through the whole cycle and what the expected response codes were!

但是我知道某处必须有一个标准的DDNS API。 我浏览了一些受支持的提供程序，发现https