| 11 Sep 2025 |
 @saiko:knifepoint.net | at that point I would set up a normal dns server with a non-local. zone and use normal dns. I’m just making a somewhat educated guess here so I might be wrong but for this to work with mdns names I assume you need a modified mdns resolver on the client, or serve the local. zone via dns which is forbidden | 15:43:22 |
 ghostbuster91 | ok let me take a step back and explain my use-case. Maybe I did something wrong earlier.
I have headscale that has global dns configured that point to my adguard instance.
| 15:45:06 |
| ghostbuster91 | There I have manual entries xyz.mydomain that points to my serwer (by the vpn ip adderss) | 15:45:39 |
| ghostbuster91 | one of them is esphome.mydomain | 15:45:46 |
| ghostbuster91 | this works great until I want to explore one of the devices listed in esphome dashboard | 15:46:07 |
| ghostbuster91 | this devices advertise themselves by mDNS | 15:46:20 |
| ghostbuster91 | once I am on the vpn I can see the esphome dashboard by I cannot enter into any device | 15:46:43 |
| ghostbuster91 | * once I am on the vpn I can see the esphome dashboard by I cannot enter into any device's details | 15:46:51 |
| ghostbuster91 | * these devices advertise themselves by mDNS | 15:47:16 |
| @saiko:knifepoint.net | can you make the dashboard proxy the info instead of requiring the client to access the devices directly, or set non-mdns names for the devices? | 15:48:04 |
| @saiko:knifepoint.net | otherwise if this can’t be changed I would really just use openvpn or some othe tap tunnel | 15:48:32 |
| @saiko:knifepoint.net | and then it should just work | 15:48:39 |
 toonn | K900: Do you have a way of getting mDNS to work over Tailscale? | 15:48:42 |
| ghostbuster91 | I don't think so. The info pages use websockets to propagate realtime information | 15:49:34 |
| ghostbuster91 | Yeah that would work | 15:49:52 |
