Bug: *.host not resolved on WARP for Linux & Windows

Update: WARP for Windows is affected too.

I’m having issues resolving .HOST domains when connected to WARP. This happens Linux (version 2022.5.346) and Windows (version 2022.7.174.0). Mac doesn’t seem to be affected.

From the current 1488 top-level domains, .HOST is the only one that doesn’t work.

After checking the logs (warp-cli -l enable-dns-log) I notice that any query I make it’s shown on the logs EXCEPT when querying anything under the .HOST top-level domain. I bet the domain HOST is hardcoded somewhere in the source and manually filtered from being resolved and hence not being added to the logs.

It happens when querying 127.0.2.2 or 127.0.2.3 that are set by WARP on /etc/resolv.conf

Some basic query to be sure it resolves other queries:

$ host -t a cloudflare.com 127.0.2.2
Using domain server:
Name: 127.0.2.2
Address: 127.0.2.2#53
Aliases:

cloudflare.com has address 104.16.133.229
cloudflare.com has address 104.16.132.229

Query to get the root DNS server for *.host:

$ host -t ns host. 127.0.2.2
;; connection timed out; no servers could be reached

Query to get the A records for one of the root servers for the TLD host.

$ host -t a f.nic.host 127.0.2.2
;; connection timed out; no servers could be reached

How to reproduce:

Install WARP on Linux.
Connect and try to resolve nic.host
Check the dns logs and you’ll never see the query.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.