Stop faffing around with duckdns and use Tailscale - eviltoast

I’ve been trying for yonks (>two full days, plus crashing HA along the way) to get duckdns to work on my home assistant, so that I can remote access it from my telephone. Without success. There are pages and pages of people trying to get it to work, with multiple suggestions, mostly without success. I then came across Tailscale, it took me all of ten minutes to set it up, and WORKING. Whow, so hope this helps anybody trying to get remote access to their home assistant. This is not a publicity for Tailscale or Duckdns, just I’m so pleased to get it finally working.

  • forbiddenlake@fedia.io
    link
    fedilink
    arrow-up
    9
    ·
    1 year ago

    Tail scale is great but the way its magic dns works has broken my device’s Internet more than thrice. Primarily on Android (there’s a long standing bug report) but also on Linux (before I fixed the firewall). If Android is your primary device I would absolutely not recommend tail scale for ha.

    The problem is that to make magic dns work, it has to override your local dns settings, which is fine until it breaks. For example, if private DNS is enabled in Android (which it is by default) then when your phone switches networks, dns straight up doesn’t work until you toggle TS off and on. Which means your internet doesn’t work. And magic dns is “needed” to get a TS https certificate (if you have another valid cert, this is less important).

    On my Android I have private DNS on and a tasker profile to toggle TS whenever the network changes. It is not ideal.