Tailscale address resolving using internal DNS servers is not working
11:16 26 Feb 2025

I configured a subnet for my internal server network 192.168.77.0/24 on a Linux machine, have advertized this subnet on the linux node and have approved it on the Dashboard. From other authorized nodes I can connect via IP to internal service.

In the DNS, I've added my two DNS servers 192.168.77.11 and 192.168.77.13 restricted to internal-mvp.ch, and I've added a search domain for my internal domain intranet-mvp.ch.

I can access internal addresses, but the DNS does not resolve short or long names. Using tailscale dns query the long address resolves. But using nslookup it does not. The short address fails on both.

C:\Users\olivier.boudry\Downloads>tailscale dns status

=== 'Use Tailscale DNS' status ===

Tailscale DNS: enabled.

Tailscale is configured to handle DNS queries on this device.
Run 'tailscale set --accept-dns=false' to revert to your system default DNS resolver.

=== MagicDNS configuration ===

This is the DNS configuration provided by the coordination server to this device.

MagicDNS: enabled tailnet-wide (suffix = tailxxxxxx.ts.net)

Other devices in your tailnet can reach this device at mvp-wksch-0190.tailxxxxxx.ts.net.

Resolvers (in preference order):
  (no resolvers configured, system default will be used: see 'System DNS configuration' below)

Split DNS Routes:
  - intranet-mvp.ch                -> 192.168.77.11
  - intranet-mvp.ch                -> 192.168.77.13
  - ts.net.                        -> 199.247.155.53
  - ts.net.                        -> 2620:111:8007::53

Search Domains:
  - intranet-mvp.ch
  - tailxxxxxx.ts.net

=== System DNS configuration ===

This is the DNS configuration that Tailscale believes your operating system is using.
Tailscale may use this configuration if 'Override Local DNS' is disabled in the admin console,
or if no resolvers are provided by the coordination server.

Nameservers:
  - 172.20.10.1

Search domains:
  (no search domains found)

[this is a preliminary version of this command; the output format may change in the future]

C:\Users\olivier.boudry\Downloads>tailscale dns query apsrepository
DNS query for "apsrepository" (A) using internal resolver:

Multiple resolvers available:

Response code: RCodeServerFailure

No answers were returned.

C:\Users\olivier.boudry\Downloads>tailscale dns query apsrepository.intranet-mvp.ch
DNS query for "apsrepository.intranet-mvp.ch" (A) using internal resolver:

Multiple resolvers available:
  - 192.168.77.11
  - 192.168.77.13

Response code: RCodeSuccess

Name                            TTL   Class      Type   Body
----                            ---   -----      ----   ----
apsrepository.intranet-mvp.ch.  3600  ClassINET  TypeA  192.168.77.14

C:\Users\olivier.boudry>nslookup
Serveur par dÚfaut :   UnKnown
Address:  172.20.10.1

> mvpsrv-file
Serveur :   UnKnown
Address:  172.20.10.1

*** UnKnown ne parvient pas à trouver mvpsrv-file : Non-existent domain
> mvpsrv-file.intranet-mvp.ch
Serveur :   UnKnown
Address:  172.20.10.1

*** UnKnown ne parvient pas à trouver mvpsrv-file.intranet-mvp.ch : Non-existent domain
> server 100.100.100.100
Serveur par dÚfaut :   [100.100.100.100]
Address:  100.100.100.100

> mvpsrv-file
Serveur :   [100.100.100.100]
Address:  100.100.100.100

Nom :    mvpsrv-file.intranet-mvp.ch
Address:  192.168.77.39

> mvpsrv-file.intranet-mvp.ch
Serveur :   [100.100.100.100]
Address:  100.100.100.100

Nom :    mvpsrv-file.intranet-mvp.ch
Address:  192.168.77.39

> exit

C:\Users\olivier.boudry>ping 192.168.77.39

Envoi d’une requête 'Ping'  192.168.77.39 avec 32 octets de données :
Réponse de 192.168.77.39 : octets=32 temps=96 ms TTL=126
Réponse de 192.168.77.39 : octets=32 temps=51 ms TTL=126
Réponse de 192.168.77.39 : octets=32 temps=62 ms TTL=126
Réponse de 192.168.77.39 : octets=32 temps=120 ms TTL=126

Statistiques Ping pour 192.168.77.39:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 51ms, Maximum = 120ms, Moyenne = 82ms

C:\Users\olivier.boudry>

It looks like Tailscale DNS works fine but is not the default DNS for my wifi connection. My client is setup to use Tailscale DNS, I would expect it to amend configuration and force Tailscale DNS. Am I doing something wrong ?

dns tailscale