EdgeRouter X + DNS Routing: Do I even need DuckDNS on HA?

I finally had the time to set up a Ubiquiti EdgeRouter on my network. (Weird set up due to AT&T which I’ll put into a blog post.)

The EdgeRouter has DNS Forwarding (sometimes known as “split horizon dns”) which will allow me to forward traffic to the correct service/IP on my LAN.

So, requests sent to “myhassiobox.com” will get forwarded to my Hassio installation on my RPi4 while requests sent to “mynextcloud.com” will get sent to my NextCloud insallation. It’ll even forward to the correct port if I’m running multiple services on the same box.

The EdgeRouter supports Dynamic DNS natively using dyndns, dnspark, loopia and “URL,” which I’m hoping let’s me use the service of my choice.

With this set up, do I even need to set up the DuckDNS integration in Hassio?

Does anyone have a perspective or experience with this?

Many routers support a dynamic dns service. However you will be missing the let’s encrypt side of the ducks a add on.

Encrypting the traffic you send to your HA instance when out and encrypting the info before it goes back out is important.

The add on is a few clicks to setup and super stable. I’d say go with it.

Thanks @silvrr.

Yes, I intend to make sure the data is encrypted. There’s a Let’s Encrypt add-on for HA, independent of the DuckDNS add-on.

With that in mind, would that change your recommendation?

I would just run the add on.

Hello, can u help me how to direct myhassdomain.com to local ip address of HA running on a pi4? Where in edgerouters setting i can set this?

Hi, Usman. I went in a different direction to accomplish this, so I’m not sure how to do it on the EdgeRouter.