daemon fails to start if Windows hostname is > 15 letters

[VariableDeclared]

Description
When starting the docker daemon on Windows 10 build 1903 the daemon fails to start with error "Could not resolve host..."

Steps to reproduce the issue:

1. Install Windows 10 1903, latest as of writing
2. Set a computer name greater than 15 characters. (Advanced System Settings > Computer Name)
3. Restart
4. Try to start the docker daemon.

Describe the results you received:

Docker daemon fails with error:

The computer 'WINDOWS10DEMOMA' could not be resolved. Make sure you typed the machine name correctly and that you have network access.

full log here

Describe the results you expected:

Docker Desktop starts.

Additional information you deem important (e.g. issue happens only occasionally):

Make sure hostname is greater than 15 not equal to, when setting hostname equal to 15 or less than, this issue does not arise.

I suspect this has to do with the internals of NETBIOS and Windows name resolution, but didn't get the chance to investigate. When setting a hostname > 15 characters you do get a warning that NETBOIS can only work with names of length 15 bytes.

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:26:49 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Output of docker info:
Client can't connect to daemon for obvious reasons, but output given below.

Client:
 Debug Mode: false

Server:
ERROR: Error response from daemon: i/o timeout
errors pretty printing info

Additional environment details (AWS, VirtualBox, physical, etc.):

Windows 10 VM (KVM) with nested virtualisation enabled.