DNS suffix search list of other network adapters are ignored

[jamilbk]

Despite concatenating the DNS Suffix Search Lists from all network adapters, Windows doesn't actually go through the entire search list.

Here is an example of such a configuration:

Here, the Firezone admin configured example.com as the search domain for the Firezone tenant. google.com is simulated to be the search domain assigned by DHCP on the local network.

In the global configuration, Windows recognises both lists and displays both search domains but when asked to resolve a single-label domain that would succeed with the 2nd search domain, it fails.

[thomaseizinger]

• the user is trying to access their local services leveraging their local network's search domain

Isn't that essentially #8266?

[jamilbk]

• the user is trying to access their local services leveraging their local network's search domain

Isn't that essentially #8266?

Hm I don't think so exactly. Local LAN services are not related to search domains (though they may be used for similar things). Services like mDNS and LLMNR (Bonjour etc) don't rely on search domains at all right? This would be things like printer sharing SMB/NetBIOS shares.

Many people configure their local LAN search domain, but many people don't, and local LAN devices are still accessible using multicast DNS services. In my local network for example, my ISP sets a search domain att.net.

[thomaseizinger]

Should I update the docs to make this a known issue?

[jamilbk]

Yeah good call

[jamilbk]

It seems that in some cases Android might also suffer from this, since we become the default resolver on the system there.