dig +trace is not working when using DNS tunnel 10.255.255.254

[CHfish-ch]

Windows Version

10.0.22631.4169

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• 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 .)

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Name resolution fails with VPN & dnsTunneling (#10520), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[CHfish-ch]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[CatalinFetoiu]

thanks for reporting the issue and sending logs
it looks like the WslNetworkingLogs zip you sent is missing the logs.etl file - can you please collect networking logs again and double check if the logs.etl file is present? (that file contains DNS logs that are needed to investigate this issue)

please feel free to send the new logs on the same email