Tailscale DNS resolution failure preventing .ts.net hostname resolution in VirtualBox VM

### What is the issue?

A VirtualBox virtual machine (VM) running Void Linux is unable to resolve hostnames within the Tailscale network (e.g., .ts.net). The VM is configured to use the Tailscale IP address of the Windows host machine as its DNS server. While basic network connectivity over Tailscale is confirmed between the VM and the Windows host, DNS queries from the VM are not being resolved.

Specifically:

The Void Linux VM sends DNS queries to the Windows host's Tailscale IP on port 53.

No DNS responses are received by the VM.

The Tailscale adapter on the Windows host shows "No Internet access" and "No network access".

Troubleshooting Steps Taken
The following steps have been taken to diagnose and resolve the issue:

Verify basic Tailscale connectivity: Ping tests confirm that the Void Linux VM and the Windows host can communicate over the Tailscale network.

Check Windows Firewall: The Windows Firewall has been temporarily disabled to rule out any firewall interference.

Restart Tailscale service: The Tailscale service on the Windows host has been restarted multiple times.

Reboot Windows host: The Windows host has been rebooted.

Examine Tailscale logs: The Tailscale logs on the Windows host are encrypted and not human-readable.

Generate Tailscale bug report: A Tailscale bug report has been generated with the following ID:

BUG-feb4bd4184be10601d66fabe5b2323fc0f07988ea83c0c0d8c00095c8745ee32-20250426195836Z-0ab43f977324e677

Root Cause (Suspected)
The root cause is suspected to be an issue with how the Windows host is handling DNS requests within the Tailscale network. The "No Internet access" status on the Tailscale adapter suggests a problem with the host's ability to route or process DNS queries for Tailscale.

The Tailscale adapter on my Windows 10 Pro host is missing IPv4 DNS server addresses.

ipconfig /all and Get-DnsClientServerAddress confirm that the IPv4 configuration of the Tailscale adapter has no DNS servers assigned (ServerAddresses: {}).

The adapter does have IPv6 DNS servers assigned (fec0:0:0:ffff::1, etc.), but these are not used for IPv4 queries.

Because of this, my Windows host cannot resolve .ts.net hostnames over IPv4, which is why my Void Linux VM (sending IPv4 DNS queries to the host's Tailscale IP) is failing to resolve Tailscale hostnames

### Steps to reproduce

REsolving Hostname

### Are there any recent changes that introduced the issue?

_No response_

### OS

Linux

### OS version

Void

### Tailscale version

1.82.5

### Other software

_No response_

### Bug report

BUG-feb4bd4184be10601d66fabe5b2323fc0f07988ea83c0c0d8c00095c8745ee32-20250426195836Z-0ab43f977324e677