dig +trace is not working when using DNS tunnel 10.255.255.254

### Windows Version

10.0.22631.4169

### WSL Version

2.2.4.0

### Are you using WSL 1 or WSL 2?

- [X] WSL 2
- [ ] WSL 1

### Kernel Version

5.15.153.1-microsoft-standard-WSL2

### Distro Version

Ubuntu 22.04

### Other Software

dig 9.18.28-0ubuntu0.22.04.1-Ubuntu

### Repro Steps

`dig +trace www.microsoft.com`

### Expected Behavior

generated by using `dig -4 +trace www.microsoft.com @8.8.8.8`
```
; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> -4 +trace www.microsoft.com @8.8.8.8
;; global options: +cmd
. 87203 IN NS c.root-servers.net.
. 87203 IN NS m.root-servers.net.
. 87203 IN NS k.root-servers.net.
. 87203 IN NS l.root-servers.net.
. 87203 IN NS d.root-servers.net.
. 87203 IN NS a.root-servers.net.
. 87203 IN NS h.root-servers.net.
. 87203 IN NS b.root-servers.net.
. 87203 IN NS e.root-servers.net.
. 87203 IN NS i.root-servers.net.
. 87203 IN NS f.root-servers.net.
. 87203 IN NS g.root-servers.net.
. 87203 IN NS j.root-servers.net.
. 87203 IN RRSIG NS 8 0 518400 20241003050000 20240920040000 20038 . GQ5NmgbfVq2uGVa6PmIcZnBmgmXQrHjSkaZc/j2qV8GRrRRSeiJencIj U3TscIjs8EmYGvZ2L5f0hwkndrASb+Je5/5OnzuZxpdBdNXI925wYL3w buuThPJMTXx7ovcFQc0xx5l+Yr07a1BDl3GK7GatPQjwCOsB30dy+qMk VuPzv3NfzWKcQw/52G843xkpCaoTRcNpZfwhX+oCVGBeWsNoSS/riVLG /UBu0WvHZukfFTLhLN+Vb/9rh4tDdihiWBUr6oItCuW5DjajCo/UP2xy JKvWkH2SwT6tMt7asaEczuVry5Hc3KSDtXDlxjU21DONDSBNT8W0aaNc 5SJn+Q==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 10 ms

com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 86400 IN DS 19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D7 71D7805A
com. 86400 IN RRSIG DS 8 1 86400 20241003050000 20240920040000 20038 . Sx7Tcq7BJSIvOyGM6h8iRN30hWo7udcFkuxjacruAdd0vHEsv2VVo1Sq K3QMqwyStD1JqsRm4lUHBchzl1+AcHhKAjmZFFV0frn9+s7vadUf0tdh YVU2fK4DQNzioCKc6szkC3BKAi0INsQbZL6WsUlIYqcyQn+NgViUC8b7 34Qs2BdhXQ2Qm7PDnkuzrMqfvaIKbzVIDTA1OJn8qR2BIw37haDaVxpV CuCuaVM7WJ2hJQbGNz1z4gV190Kob52AqByGAg+ndwv/wjTzZazGrUQB +/5PsVo1IEq8MqBzGd5Fc9aTgwYzXWhLFoK6p/lJcAacEl3Y90QusJT7 5TSz/Q==
;; Received 1208 bytes from 192.33.4.12#53(c.root-servers.net) in 19 ms

microsoft.com. 172800 IN NS ns1-39.azure-dns.com.
microsoft.com. 172800 IN NS ns2-39.azure-dns.net.
microsoft.com. 172800 IN NS ns3-39.azure-dns.org.
microsoft.com. 172800 IN NS ns4-39.azure-dns.info.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q3UDG8CEKKAE7RUKPGCT1DVSSH8LL NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 13 2 86400 20240925002558 20240917231558 59354 com. xlZZclCSCVpTMUvFVF2tWnGIuEUFZC++DaBK0Kl5T2h6WgtSTA0yyo/M t0rtDYdAGWoP+eC7xK2LJucv15cxYw==
TCQ78V56RPB9M9CO6K6FI9UOGRT276QB.com. 86400 IN NSEC3 1 1 0 - TCQ7UPE9KKP7O5334RKPO6Q0OGVO6N8T NS DS RRSIG
TCQ78V56RPB9M9CO6K6FI9UOGRT276QB.com. 86400 IN RRSIG NSEC3 13 2 86400 20240925014005 20240918003005 59354 com. T2NcBkwmS5iqmLN7ZWv5meprIov0Fe2nz0eSIxHLTvdhAPd9V8uQLoxO ioRF/3wiIMHEcowGDzX/eN8hu0UakA==
;; Received 553 bytes from 192.52.178.30#53(k.gtld-servers.net) in 19 ms

www.microsoft.com. 3600 IN CNAME www.microsoft.com-c-3.edgekey.net.
;; Received 93 bytes from 13.107.222.39#53(ns3-39.azure-dns.org) in 9 ms
```

### Actual Behavior

`;; communications error to 10.255.255.254#53: timed out`

### Diagnostic Logs

the reason of the behavior seems to be the missing answer of the DNS tunneling endpoint 10.255.255.254 to the query of the DNS root zones (`dig NS .`)

No source files or tests are named. Reproduce the issue in WSL 2 on Ubuntu 22.04 with `dig +trace www.microsoft.com`, compare it with the `-4` query directed at `8.8.8.8`, and investigate the DNS tunneling endpoint's response to `dig NS .`; done means recursive tracing no longer times out at 10.255.255.254.

Written by the indexing model from the issue text.