3

Windows client: proxy service crashes when exclude domain is specified

I have installed the Windows client version 3.0.12 in an Active Directory domain member computer. To ensure that the local domain (which is not resolvable by Internet DNS servers) can be resolved on the client, I specified the local domain as an excluded domain using the EXCLUDE_DOMAINS argument when installing (according to the Windows Client Mass Deployment Guide).

Whenever I attempt to perform a DNS query for a resource in the excluded domain, the NextDNS DNS53 to DoH proxy. service crashes and restarts rapidly and repeatedly and subsequent DNS queries fail, to either internal or external (Internet) domains.

This makes the Windows client basically unusable in a Windows Active Directory domain. Without the client, we can still use NextDNS servers as forwarders in our Active Directory DNS server, but we lose the benefit of per-machine logging.

10 replies

null
    • Jonathan_Johnson
    • 1 yr ago
    • Reported - view

    I have tried this on several different computers in different domains and networks and had the same results.

    • Dustin.3
    • 3 mths ago
    • Reported - view

    NextDNS, I have the same issue.  I'm evaluating the product and the Windows client crashes when resolving a *.local hostname (that is part of the exclusion list).  PC is running the latest update of Windows 11 and the client software.

     

    The only error message I can find is from Windows' event viewer.  The NextDNS client log file resets when the service crashes.  For now I'm evaluating using YogaDNS on our remote laptops instead.

    • Lumineer
    • 2 mths ago
    • Reported - view

    Heyo,

     

    I personally do it though the configureations for IPv4 and 6 and just using the DNS through that, oh and through my router.

    • Daniele_Capuano
    • 4 wk ago
    • Reported - view

    I am also experiencing the exact same issue on multiple computers in several domains.

    This only happens on devices where a .local domain is excluded.

     

    Any ideas?

    • Dustin.3
    • 4 wk ago
    • Reported - view

    I ended up using DNSFilter.com for our office instead of NextDNS. Their Windows client is stable and works well. Pricing isn't too bad.

    • Drago.1
    • 4 wk ago
    • Reported - view

    I have the same problems with all installation.  If any domain is present in bypass settings of client NextDNS, the service crashes.

    I refuse to think that the NextDNS team has do not considered this issue.

    • Atmis
    • 3 wk ago
    • Reported - view

    The Windows client is barely unusable in a corporate environment because of that issue. I have deployed 10 PCs, the service crashes on most of them during the workday, making it totally unreliable.

    Is the Windows client still on active development ?

    I tried using native DoH in Windows, using the command Add-DnsClientNrptRule to forward the local domain to the company DNS server. But the DoH configuration is not propagated automatically to Ethernet interfaces that are added later (this is the case as we are using  docking stations).

    • Atmis
    • 3 wk ago
    • Reported - view

    Would it be possible to have a status from the staff on that issue? I can see recent updates on other issues.

    I have been a personal subscriber for 2 years, and I decided to subscribe also for an enterprise plan for my small company. NextDNS service is great overall, but not having a reliable client is a pity.  And it is a long-known problem!

    Looking forward to hearing from you.

      • Drago.1
      • 3 wk ago
      • Reported - view

       i sent an email but i didn't receive any reply.

      • Atmis
      • 3 wk ago
      • Reported - view

      Thanks  for your input

      I removed the domain exclusion on some PCs here, but the client continues to crash.

      So I finally went native DoH with a PowerShell script to setup the configuration, but it is not that easy.

Login to reply

Content aside

  • 3 Likes
  • 3 wk agoLast active
  • 10Replies
  • 131Views
  • 6 Following