PSA: make sure to allow your CI to access your DNS server inside the Tailscale ACL

Open
#116 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, kubernetes
Domain
ci-cd, infrastructure, networking

Research direction

The issue names no file, test, or entry point. First identify where CI connectivity or Tailscale ACL guidance belongs, then document access for the tag:ci identity to the custom DNS server and verify the guidance against MagicDNS, CoreDNS, and Kubernetes.

Written by the indexing model from the issue text.

Description

I was having issues with DNS solving.

The reason was that I didn't allow the "tag:ci" to allow my custom DNS server inside my ACL (it drops everything by default).

(I am using MagicDNS + a CoreDNS server running inside Kubernetes)

Dominant language
TypeScript
Stars
938
Forks
137
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tailscale/github-action

All issues in tailscale/github-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.