After Latest Update DNS Short Names Not Properly Resolved

### What is the issue?

DNS shortnames do not seem to be working properly. Tailscale is running on servers hosted in AWS, I only use to it access my AWS servers externally. Servers in AWS point to a private, internal DNS server.

For brevity:
S1: Ubuntu 22.04.4/Linux 6.5.0-1023-aws on | Tailscale 1.72.1
S2: Windows Server 2008 | Tailscale 1.44.3 (DNS Server)
S3: Windows Server 2022 | Tailscale 1.72.0

When run from S1 where S2 and S3 are DNS shortnames:
ping S2, fail
ping S3, success
ping S2.MYPRIVATEDOMAIN.COM, success
ping S3.MYPRIVATEDOMAIN.COM, success

EDIT: I can ping S1 from S2 and S3 with success as well as S3 to S2.

Turning Tailscale off, all of the above succeed. MagicDNS is turned off. Override LocalDNS is not enabled either. Same behavior with nslookup.

S2 happens to be WIndows Server 2008 and running the old version of Tailscale. Not sure if this is relevant.

/run/systemd/resolve/stub-resolv.conf

nameserver 127.0.0.53
options edns0 trust-ad
search MYPRIVATEDOMAIN.COM

resolvectl status (partial)
Link 2 (enp39s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.234
DNS Servers: 192.168.1.234 // the correct location of my internal dns
DNS Domain: MYPRIVATEDOMAIN.COM

### Steps to reproduce

See above

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

I ran apt-get upgrade as well as updated Tailscale to the latest version.

### OS

Linux, Windows

### OS version

Ubuntu 22.04.4 LTS/ Linux 6.5.0-1023-aws

### Tailscale version

1.72.1, 1.44.3

### Other software

- Docker
- NGINX Proxy Manager

### Bug report

BUG-6e1009047330d20a362aaf1c103bae21645da2f651839dfcb6fcad9c928f86ed-20240905225642Z-c9546f9126e408e2