Content-Length: 204982 | pFad | http://github.com/tailscale/tailscale/issues/14746

F3 Custom DNS resolver not properly configured on macOS · Issue #14746 · tailscale/tailscale · GitHub
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

Custom DNS resolver not properly configured on macOS #14746

Open
phearnot opened this issue Jan 23, 2025 · 0 comments
Open

Custom DNS resolver not properly configured on macOS #14746

phearnot opened this issue Jan 23, 2025 · 0 comments
Labels
bug Bug needs-triage

Comments

@phearnot
Copy link

What is the issue?

I'm running the Pi-hole on one of the machines on my tailnet. As described in the howto, I've added the machine which is running Pi-hole as the global resolver on the DNS tab, ticked the 'Override local DNS' checkbox and disabled MagicDNS. I'm expecting Tailscale to configure macOS to use the resolver I've configured.

However, even with Tailscale DNS enabled in the client, macOS uses 100.100.100.100 instead of the resolver I've configured. Here's the output of 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: disabled tailnet-wide.

Resolvers (in preference order):
  - 100.108.239.10

Split DNS Routes:
  (no routes configured: split DNS disabled)

Search Domains:
  (no search domains configured)

=== 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:
  - fe80::1%en0
  - 192.168.0.1
  - 192.168.0.1

Search domains:
  (no search domains found)

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

Note that custom resolver (100.108.239.10) is configured. Here's what macOS reports as being used:

❯ scutil --dns
DNS configuration

resolver #1
  search domain[0] : lan
  nameserver[0] : 100.100.100.100
  if_index : 22 (utun4)
  flags    : Supplemental, Request A records, Request AAAA records
  reach    : 0x00000003 (Reachable,Transient Connection)
  order    : 100000

resolver #2
  nameserver[0] : fe80::1%en0
  nameserver[1] : 192.168.0.1
  nameserver[2] : 192.168.0.1
  if_index : 14 (en0)
  flags    : Request A records, Request AAAA records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)
  order    : 200000

resolver #3
  domain   : local
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 300000

resolver #4
  domain   : 254.169.in-addr.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 300200

resolver #5
  domain   : 8.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 300400

resolver #6
  domain   : 9.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 300600

resolver #7
  domain   : a.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 300800

resolver #8
  domain   : b.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records, Request AAAA records
  reach    : 0x00000000 (Not Reachable)
  order    : 301000

DNS configuration (for scoped queries)

resolver #1
  search domain[0] : lan
  nameserver[0] : fe80::1%en0
  nameserver[1] : 192.168.0.1
  nameserver[2] : 192.168.0.1
  if_index : 14 (en0)
  flags    : Scoped, Request A records, Request AAAA records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

resolver #2
  nameserver[0] : 100.100.100.100
  if_index : 22 (utun4)
  flags    : Scoped, Request A records, Request AAAA records
  reach    : 0x00000003 (Reachable,Transient Connection)

So instead of the resolver I've configured, Tailscale appears to be setting 100.100.100.100 as the default resolver.

Steps to reproduce

No response

Are there any recent changes that introduced the issue?

No response

OS

macOS

OS version

macOS Sequoia 15.1.1 (24B2091)

Tailscale version

1.78.1

Other software

No response

Bug report

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Bug needs-triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@phearnot








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/tailscale/tailscale/issues/14746

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy