Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DNS caching on clients #1430

Closed
DentonGentry opened this issue Mar 3, 2021 · 2 comments · Fixed by #1476
Closed

DNS caching on clients #1430

DentonGentry opened this issue Mar 3, 2021 · 2 comments · Fixed by #1476
Labels
L3 Some users Likelihood OS-windows P5 Halts deployment Priority level

Comments

@DentonGentry
Copy link
Contributor

(copied from initial report of the problem):

Problem: When connecting to tailscale, clients have cached DNS entries and can no longer access services

Steps:

  1. Use workstation out of corporate campus on the internet
  2. Machine caches external DNS records
  3. Machine joins tailscale
  4. DNS record is cached, yet tailscale is configured with DNS servers that should be used, to enable service access

Proposed Solution Ideas:

If DNS is configured in the tailscalepolicy, flush DNS on connection to tailscale.
@DentonGentry
Copy link
Contributor Author

It seems fine to exec ipconfig to flush the cache.

peske added a commit that referenced this issue Mar 10, 2021
@peske
wgengine/router: flushdns in windows when router config changes
97b6b88 
Fixes: #1430
Signed-off-by: Aleksandar Pesic <peske.nis@gmail.com>
@peske peske mentioned this issue Mar 10, 2021
Merged
peske added a commit that referenced this issue Mar 13, 2021
@peske
wgengine/router: flushdns in windows when router config changes
8ef3dca 
Fixes: #1430

Signed-off-by: Aleksandar Pesic <peske.nis@gmail.com>
peske added a commit that referenced this issue Mar 15, 2021
@peske
wgengine/router: flushdns in windows when router config changes
25d2dd8 
Fixes: #1430

Signed-off-by: Aleksandar Pesic <peske.nis@gmail.com>
jonrzhang pushed a commit to jonrzhang/tailscale that referenced this issue Mar 16, 2021
@peske @jonrzhang
wgengine/router: flushdns in windows when router config changes
743b1fb 
Fixes: tailscale#1430

Signed-off-by: Aleksandar Pesic <peske.nis@gmail.com>
@DentonGentry DentonGentry reopened this Aug 3, 2021
@DentonGentry
Copy link
Contributor Author

Tracking this elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
L3 Some users Likelihood OS-windows P5 Halts deployment Priority level
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

flushdns in windows when router config changes tailscale/tailscale
2 participants
@DentonGentry @peske