Skip to content

Fix Tailscale DNS docs: Extra records are not a Tailscale UI - #73

Merged
shangeethsivan merged 1 commit into
mainfrom
cursor/tailscale-dns-no-extra-records-93f5
Sep 2, 2026
Merged

shangeethsivan merged 1 commit into
mainfrom
cursor/tailscale-dns-no-extra-records-93f5

Conversation

@shangeethsivan

Copy link
Copy Markdown
Owner

Tailscale’s DNS page has MagicDNS, Nameservers, and Split DNS. It does not have Extra records — that control was never shipped (Tailscale DNS docs).

This updates docs/tailscale-admin.md (and the in-app help pointer) to the options that actually exist:

  • Railway: no 100.x bind; trial/hobby is often one custom domain, so admin.syncidian.com cannot be attached next to syncidian.com. Keep SYNCIDIAN_ADMIN_HOST unset and use /admin.
  • Operator laptop: /etc/hosts (or Split DNS + Pi-hole).
  • Self-host on a Tailscale node: public A → 100.x, or the machine’s *.ts.net MagicDNS name.

No runtime behavior change except the help copy.

Open in Web Open in Cursor 

Tailscale never shipped an Extra records UI on the DNS page.
Document hosts file, Split DNS + Pi-hole, public A to 100.x, and
the Railway one-custom-domain limit instead.

Co-authored-by: shangeeth95 <shangeeth95@gmail.com>
@shangeethsivan
shangeethsivan marked this pull request as ready for review September 2, 2026 20:05
@shangeethsivan
shangeethsivan merged commit f4add66 into main Sep 2, 2026
1 check passed
@shangeethsivan
shangeethsivan deleted the cursor/tailscale-dns-no-extra-records-93f5 branch September 3, 2026 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants