Cannot access other Tailnet device from HA using MagicDNS name (Tailscale)

Hello, I have installed and configured the Tailscale add-on and I can access my HA correctly from other devices in my Tailnet using SSL with it’s MagicDNS name (ex. https://homeassistant.my-tailnet.ts.net). All good there.

My trouble is trying to access other devices on the Tailnet from HA using their MagicDNS names (ex. https://jellyfin.my-tailnet.ts.net). I have disabled the userspace_networking config and I can access other devices in the Tailnet using only by their IP address, but if I try to ping using the MagicDNS name I get this error: ping: bad address 'jellyfin.my-tailnet.ts.net'

In the Tailscale add-on documentation it says:

To be able to address those clients not only with their tailnet IP, but with their tailnet name, you have to configure Home Assistant’s DNS options also.

I don’t know what DNS configuration I need to do here.

Any help would be appreciated :slight_smile:

Tailscale config:

advertise_exit_node: false
advertise_connector: false
advertise_routes: []
log_level: debug
proxy: true
tags:
  - tag:homeassistant
userspace_networking: false

Ping logs (from HA web terminal)

➜  ~ ping 100.xxx.xxx.xxx
PING 100.xxx.xxx.xxx (100.xxx.xxx.xxx): 56 data bytes
64 bytes from 100.xxx.xxx.xxx: seq=0 ttl=64 time=111.342 ms
64 bytes from 100.xxx.xxx.xxx: seq=1 ttl=64 time=1.683 ms
64 bytes from 100.xxx.xxx.xxx: seq=2 ttl=64 time=1.716 ms
^C
--- 100.xxx.xxx.xxx ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.683/38.247/111.342 ms
➜  ~ ping jellyfin.my-tailnet.net
ping: bad address 'jellyfin.my-tailnet.ts.net'

Hi, take a look at How to make Home Assistant resolve MagicDNS endpoints without losing the ability to resolve anything non-MagicDNS? · hassio-addons/addon-tailscale · Discussion #449 · GitHub – I hope it will work for you as well.