TAILMON TAILMON v1.3.0 -Aug 24, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Available in AMTM!)

[jksmurf]

I don't use TAILMON but it looks like you would add it to your custom command line (4):

CMD="--advertise-routes=192.168.9.0/24,192.168.53.15/32 --accept-dns=false"

Yep, seems to have done the trick!

No endless loops, I can see the names in /et/resolv.conf

nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 2606:4700:4700::1111
nameserver 2606:4700:4700::1001

Thanks as always @ColinTaylor

[EDIT2] Acknowledging I am also trying an unstable track version due to this development (but now reveretd to stable), it seems not to be able to reach the DNS servers in any case, but only the local one.

# Health check:
#     - This is an unstable version of Tailscale meant for testing and development purposes. Please report any issues to Tailscale.
#     - Tailscale can't reach the configured DNS servers. Internet connectivity may be affected.

Tailscale Service Options (Custom Mode)
PRECMD: modprobe tun
ARGS: --state=/opt/var/tailscaled.state --statedir=/opt/var/lib/tailscale
PREARGS: nohup

Tailscale Connection Commandline
--advertise-routes=192.168.9.0/24,192.168.53.15/32 --accept-dns=false

  21s / 35% [e=Exit] [Selection?  ]

# Health check:
#     - This is an unstable version of Tailscale meant for testing and development purposes. Please report any issues to Tailscale.

Tailscale Service Options (Custom Mode)                                                                                                     
PRECMD: modprobe tun
ARGS: --state=/opt/var/tailscaled.state --statedir=/opt/var/lib/tailscale
PREARGS: nohup

Tailscale Connection Commandline                                                                                                           
--advertise-routes=192.168.47.0/24 --accept-dns=false

  17s / 28% [e=Exit] [Selection?  ]

[EDIT2] So I can (from my Phone (LTE)) get to the one that does not have the error message. The local one, not. Investigating...

So I thought I "fixed" the local error by selecting Enable under IPv6 "Connect to DNS Server automatically" (which meant giving up my Cloudflare IPv6 DNS) but the error came back; so not a fix.