Bug: http://deskreen.local often fails to resolve (DNS_PROBE_FINISHED_NXDOMAIN)

Prerequisites

Note: Reporting against production release v3.2.6, not a dev build. Developer prerequisite items below are N/A.

• Using yarn
• Using an up-to-date master branch
• Using latest version of devtools.
• For issue in production release, add devtools output of DEBUG_PROD=true yarn build && yarn start

Expected Behavior

Navigating to http://deskreen.local on a device browser should reliably resolve to the Deskreen host and load the Deskeen page with the screen share or other connection info.

Current Behavior

Chrome on the connecting device frequently fails to resolve http://deskreen.local, displaying:

"This site can't be reached. Check if there is a typo in deskreen.local. DNS_PROBE_FINISHED_NXDOMAIN"

This occurs in both Local and Secure sharing modes. Using the host's IP address directly as given in the Deskreen app does work.

Steps to Reproduce

1. Launch Deskreen Pro on the host machine.
2. On a connecting device (Windows 11, Chrome), navigate to http://deskreen.local.
3. Observe DNS resolution failure.

Possible Solution (Not obligatory)

Context

The .local URL is presented to users as the primary way to connect a device. When it fails, users must go back and manually type the IP address, which is less user-friendly and more error-prone, particularly for non-technical users.

Your Environment

• Node version : N/A (production release)
• Deskreen version or branch : 3.2.6
• Operating System and version : Windows 11 (latest) — both host and device; Chrome (latest) on device
• Link to your project : N/A