0

Tailscale integration uses anycast instead of ultralow

Hello,

 

This forces all traffic to Singapore, as a result most CDN activity become quite slow.

 

2 replies

null
    • Nikos
    • 3 mths ago
    • Reported - view

    I am facing a similar issue. 

    I am routed to Moscow instead of local Athens IPs.

    Since my company's policies have disallowed access to some Russian IPs when I am on taiscale +NextDNS I don't have any access to sites. When I use the company DNS, I am accessing all the sites fine.

    On the other hand even when I am sharing my phone's 5G network on my laptop I am still going to Russian IPs.

    Any ideas?

     

    thanks 

    This is a diagnostic check using my phone's network https://nextdns.io/diag/9f2bd900-b6b9-11ee-9dea-f18fc6c687fa

      • Nikos
      • 3 mths ago
      • Reported - view

      So this is tailscale related

      // TODO(bradfitz): using the NextDNS anycast addresses works but is not
// ideal. Some of their regions have better latency via a non-anycast IP
// which we could get by first resolving A/AAAA "dns.nextdns.io" over
// DoH using their anycast address. For now we only use the anycast
// addresses. The IPv4 IPs we use are just the first one in their ranges.
// For IPv6 we put the profile ID in the lower bytes, but that seems just
// conventional for them and not required (it'll already be in the DoH path).
// (Really we shouldn't use either IPv4 or IPv6 anycast for DoH once we
// resolve "dns.nextdns.io".)

      https://github.com/tailscale/tailscale/blob/main/net/dns/publicdns/publicdns.go#L103

      How do we use tailscale and NextDNS without going through the tailscale DNS integration ?

      For future visitors, I installed the NextDNS app and disabled "Override Local DNS" on tailscale console. 

      I can still access my TS devices and have better resolution

Login to reply

Content aside

  • 3 mths agoLast active
  • 2Replies
  • 117Views
  • 2 Following