1

No DNS resolution when NextDNS is set as Tailscale DNS

For the past few days, I've don't have any connectivity when connected to Tailscale with NextDNS set as Global Nameserver + "Override local DNS" option.

The moment I untick "Override local DNS" on the Tailscale admin portal, it works again

 

If I set Tailscale's DNS to any of the other default providers there are no issues. I have no custom tailnet's ACLs

This happens on my Windows 11 laptop

 

PS C:\Users\bluet> Resolve-DnsName dns.nextdns.io
Resolve-DnsName : dns.nextdns.io : This operation returned because the timeout period expired
At line:1 char:1
+ Resolve-DnsName dns.nextdns.io
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationTimeout: (dns.nextdns.io:String) [Resolve-DnsName], Win32Exception
    + FullyQualifiedErrorId : ERROR_TIMEOUT,Microsoft.DnsClient.Commands.ResolveDnsName

 

 

PS C:\Users\bluet> ping 45.90.28.132
Pinging 45.90.28.132 with 32 bytes of data:
Reply from 45.90.28.132: bytes=32 time=8ms TTL=57
Reply from 45.90.28.132: bytes=32 time=8ms TTL=57
Reply from 45.90.28.132: bytes=32 time=8ms TTL=57
Reply from 45.90.28.132: bytes=32 time=8ms TTL=57
Ping statistics for 45.90.28.132:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 8ms, Average = 8ms
PS C:\Users\bluet> ping 45.90.30.132
Pinging 45.90.30.132 with 32 bytes of data:
Reply from 45.90.30.132: bytes=32 time=204ms TTL=45
Reply from 45.90.30.132: bytes=32 time=205ms TTL=45
Reply from 45.90.30.132: bytes=32 time=204ms TTL=45
Reply from 45.90.30.132: bytes=32 time=204ms TTL=45
Ping statistics for 45.90.30.132:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 204ms, Maximum = 205ms, Average = 204ms

 

2 replies

null
    • Jordan.20
    • 11 days ago
    • Reported - view

    Same issue here, not sure if it's a NextDNS thing or a Tailscale thing but the combo is definitely causing network issues on an otherwise "open" network (no blocking or restrictive policy).  

    • Dirk
    • 10 days ago
    • Reported - view

    My issue turned out to be having another VPN (twingate) installed on the same system. Once I uninstalled it, everything returned back to normal

Content aside

  • 1 Votes
  • 10 days agoLast active
  • 2Replies
  • 91Views
  • 2 Following