1

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.

3 replies

null
    • Jonathan_Johnson
    • 11 mths ago
    • Reported - view

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

    • Dustin.3
    • 8 days 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
    • yesterday
    • 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.

Login to reply

Content aside

  • 1 Likes
  • yesterdayLast active
  • 3Replies
  • 55Views
  • 3 Following