Intermittent DNS Resolution Failures on Windows 11 with NextDNS App + Firewalla

I'm experiencing an intermittent DNS issue and I'm trying to determine whether it's related to the NextDNS Windows client, my Firewalla configuration, or a combination of both.

Environment

• Windows 11 Pro PCs
• Firewalla Gold Pro acting as router and DHCP server
• NextDNS configured on Firewalla
• NextDNS Windows app installed on the PCs
• "Report Device Name" enabled in the NextDNS app so that individual device names appear in the NextDNS logs

Issue

Occasionally a Windows PC loses the ability to resolve DNS names.

Symptoms:

• Websites do not load because hostnames cannot be resolved
• The PC still has a valid IP address
• Performing an IP release/renew obtains a new DHCP lease but does not restore DNS resolution
• Rebooting the PC immediately restores functionality

The reason I have the NextDNS app installed on the endpoints is to take advantage of device name reporting within the NextDNS dashboard. Without the app, DNS traffic appears to originate from the Firewalla rather than from individual PCs.

NextDNS Settings

The following performance settings are enabled:

• Anonymized EDNS Client Subnet
• Cache Boost
• CNAME Flattening

I don't believe these settings are the cause, but I wanted to mention them for completeness.

Questions

1. Has anyone experienced intermittent DNS failures when running both the NextDNS Windows client and NextDNS through Firewalla?
2. Is it recommended to run the NextDNS Windows app when Firewalla is already configured to use NextDNS?
3. Are there any known issues with the Windows client losing DNS resolution after DHCP lease changes, network changes, sleep/wake events, or similar conditions?
4. Is there a preferred way to maintain per-device visibility in NextDNS while still using Firewalla as the primary DNS resolver?