Steam client does not appear to support lancache.steamcontent.com

[Wully]

I have setup dns caching for steam downloads (https://lancache.net). This works fine on the Windows Steam client.

I can see in /steam/logs/content_log.txt on Windows that it enables the local content cache lookup from lancache.steamcontent.com

 
Enabling local content cache at '::ffff:c0a8:10b' from lookup of lancache.steamcontent.com.

However on the steam deck it doesn't seem to do this check for the lancache.steamcontent.com. url lookup and instead uses the normal cache*.steamcontent.com urls for downloading updates. There is nothing in the content_log.txt to indicate it is attempting to use it and I can see from my local networks DNS requests from the steamdeck that it us requesting from the normal urls.

Is there any chance of this being supported in the future? For now I can redirect all steamcontent.com urls to my local cache, but this sometimes breaks other content served by steam in the browser.

[jdancouga]

I am having this trouble as well though not on steam deck but on Linux Desktop. My windows machine uses the lancache server as expected, but my Mint 21 desktop refuses to use the cache server. If I try ping "lancache.steamcontent.com" with the steam client closed, it will resolve to the cache server IP. However, when the steam client is opened, the ping resolved IP for the "lancache.steamcontent.com" no longer points to the cache server.

[Banjo]

I'm seeing this same issue on Fedora 37, everything up to date. Same lancache and DNS config working on Windows 11 and Steamdeck.

[NullReferenceException]

Was this ever resolved. I am using the latest Ubuntu and still have no indication of the cache being used.

[fmillion]

It hasn't been resolved and seems to have even gotten worse. Before, you could add a manual host entry to /etc/hosts to get it to work. Now not only does that not seem to work, but Steam on Linux is connecting to the download servers via HTTPS, so LanCache can't do its thing even if it wanted to.

I hate to make the accusation but apparently metrics and slow downloads for people on slow links is more important than local caching. Oh, but you can download from another Steam PC...but that 1) requires being logged into the same Steam account, so doesn't do much for visitors/LAN parties, and 2) really isn't that fast - I've only ever gotten about 300 megabits via a direct gigabit Ethernet link, where with LanCache I can max out the Ethernet link to the point of lagging an SSH connection to the LanCache box.