Valve is not regularly scanning these channels. They do have a bug tracker on GitHub, though.

this is a users forum, valve devs don't come here to check for reports on a regular basis

you should go here to make a proper feature request on their GitHub issue tracker

I checked for similar requests and found none, but you should also have a look before creating a new one:
https://github.com/ValveSoftware/steam-for-linux/issues?q=label%3A%22Feature+Request%22+DNS

just remember to treat it like a developer tool, not like a forum... follow the instructions they give in the issue post model and keep it detailed but straight to the point

valve should start looking these forums but all right, thanks for the info. i am not interested to create a microsoft github account but i guess i have to.

to be fair, Valve used github since before it was bought by Microsoft, but yeah I can see the irony

unfortunately Valve's linux devs are all really really really overworked, so it's unlikely they'll have the spare time to actively scan the forums anytime soon

github also organizes issues in a near-ideal way for them to work fast through the huge pile, tagging matching similar issues that should be solved together, etc... they would have to host their own instance of gitlab or something like that, integrate steam user auth into it, then migrate the current data from github to it... not impossible, but ouch!

System wide rather than per-application seems like the more sensible place to implement DNS changes.

I've not used it but I think this does exactly that
https://github.com/m13253/dns-over-https

@jason
AFAIK DoH has been implemented per-application first (Firefox, Google Chrome, etc) so it's understandable that this approach is what people will seek out.

what an interesting alternative you found!
is it stable and secure enough for daily use already?

Indeed. It made sense for browsers to implement it first, (because it was their idea? I may be mis-remembering that) they already had the complicated HTTP stuff done.

After I wrote the above post I decided the better place to implement it would be at the local network level. Assuming you trust/are your local network administrator and have a capable router.

That particular rabbit hole lead me to the less obviously named but easier to search for package: dnscrypt-proxy https://github.com/DNSCrypt/dnscrypt-proxy

Which I can confirm is easy to setup and seems to work fine. For the past hour or so at least.