why Loss of DNS access to shares after 5.31.102 update

Following the recent 5.31.102 firmware update, many users have reported a loss of DNS-based access to shared network drives, particularly in environments relying on local hostnames rather than static IPs. This issue primarily affects users of NAS devices, such as WD My Cloud or similar systems, where mapped drives using device hostnames (e.g., \\mynas\share) suddenly become inaccessible.

The root cause appears to be a disruption in the local DNS resolution or mDNS (Multicast DNS) services after the update. Devices no longer respond to hostname-based queries, although direct IP access (e.g., \\192.168.1.10\share) still works. In some cases, the NAS may also fail to register its hostname with the local DHCP server or network router.

Possible Workarounds:

Access via IP Address: Use the NAS's static IP instead of the hostname to access shares temporarily.

Edit Local Hosts File: On Windows, add an entry to C:\Windows\System32\drivers\etc\hosts mapping the NAS hostname to its IP.

Enable NetBIOS: Ensure NetBIOS over TCP/IP is enabled in network adapter settings.

Router Reboot: Restart your router to refresh DHCP and DNS assignments.

Device Reboot and Re-registration: Reboot the NAS and verify it registers its hostname correctly on the network.

Long-Term Fix:

WD or the device vendor may need to release a patch restoring proper DNS or mDNS broadcasting functionality. Monitor the manufacturer’s support forums and firmware release notes for updates.

If the issue persists, contact customer support and reference the 5.31.102 update as the likely source. Providing feedback may also accelerate the release of a fix.