Symfonium not using headscale DNS

Support
1

App version

Production

Issue description

I have navidrome running on my homelab. I can connect with the service with a tailscale connection open. This works for me in the browser, with musly and with substreamer.

When trying to connect via Symfonium I get a resolution error. Within my headscale server I have created an A-record which resolves correctly for the aforementioned apps.

Device type

Phone

Media provider

Navidrome

Steps to reproduce

  1. Setup headscale VPS
  2. Setup homeserver with ubuntu
  3. Install tailscale on it and connect with the headscale server
  4. Run navidrome inside of incus container on ubuntu server
  5. Setup caddy on ubuntu server and forward navidrome.example.local to the incus IP with correct port
  6. Set A-record for the container in headscale config
  7. Install and setup tailscale app on an android phone
  8. Connect to the headscale instance with DNS
  9. Install symfonium and set it up with the FQDN defined in the A-record

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

tailscale-with-cloudflare_dns.log & only-tailscale.log

2

Symfonium delegate to the OS for DNS there’s nothing specific here.

2026-05-28 12:56:09.927 Verbose SubsonicLogger <-- [173] HTTP FAILED: java.net.UnknownHostException: Unable to resolve host "navidrome.xxxxx.me": No address associated with hostname

3

Hi hi,

I then wonder how it is that Musly and Substreamer are able to resolve it.

4

I don’t know there’s only a mini small extract of the logs :wink:

The up interfaces are the exact same in the 2 logs.

  • Symfonium may be excluded from the Tailscale/Headscale VPN by Android app-based split tunneling. Apps excluded from Tailscale do not have their traffic or DNS queries handled by Tailscale.
  • The other apps may use a different DNS path, for example Chrome/WebView DNS cache, DNS-over-HTTPS, an internal cache, or a custom resolver.
  • Android/Tailscale DNS settings may not be applied to the active network used by Symfonium’s app UID.
  • The Headscale extra_records entry may be correctly configured server-side, but the Android client still needs to actually use the Tailscale/Headscale DNS path to resolve it.
5

Okay… So…

I never touched the fcking split-tunneling… Symfonium was in the fcking exclusion list :face_exhaling::melting_face::melting_face:

It works now! Thanks!!! :blush::blush::blush: