Thomas Eizinger

> The caveat here being this will require a version-specific codepath. So the cool part here is that the client can't tell the difference. So this will be compatible with...

> @thomaseizinger ICE credentials are sent as part of `client_payload`? If so, we won't save any roundtrips, that message still needs to be delivered to and replied by the gateway....

The way I am thinking of implementing this is to introduce a new `setup_connection` message that will supersede `request_connection`. Perhaps we can use this change as an opportunity to split...

Handled as part of #6461.

At least on Linux, the default `systemd-resolved` configuration won't send DNS queries for single-label domains, see: https://wiki.archlinux.org/title/Systemd-resolved#systemd-resolved_does_not_resolve_hostnames_without_suffix This means, users would have to tweak their local configuration to allow resolution...

I think a better solution, at least for the usecase stated by Indevin, is for us to maybe not mess with the search domain?

It appears that we currently set a search domain of `~.`, at least on Linux: https://github.com/firezone/firezone/blob/cf874740989c9ab816ba0d714395fe477d4ab1f6/rust/headless-client/src/dns_control/linux.rs#L68-L74 I guess on Windows, the following does the equivalent: https://github.com/firezone/firezone/blob/cf874740989c9ab816ba0d714395fe477d4ab1f6/rust/headless-client/src/dns_control/windows.rs#L130 If I comment the...

> That's for the headless client We use the same module for the Tauri GUI clients.

> Disable [LLMNR](https://wiki.archlinux.org/title/Systemd-resolved#LLMNR) to let systemd-resolved immediately continue with appending the DNS suffixes That has basically the same effect as us not setting a search-domain: It will resolve hosts (aka...

> application sends connlib a query for `foo` It doesn't. DNS for hosts (aka single-label domains) is not resolved by sending a DNS query to the configured DNS server.