VSCode/VSCodium not respecting network setup contacting directly dns.google.com

Describe the bug
By inspecting network traffic, it is evident that both VSCode and VSCodium try to do some name resolution by its own method instead of following system's setup.
In the specific it tries to connect to host dns.google.com

This raises warning in the system because system's dns is configured in another way.

Tryied to execute disabling all extensions, it continues trying to do what it wants, so it is not related to any extension.

Please confirm that this problem is VSCodium-specific

This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.
I checked previous bug report that was closed for lack of info

To Reproduce
Steps to reproduce the behavior:
1 open VSCode/VSCodium
2 look at network traffic

Expected behavior
Editor should inherit and respect system's setup

Screenshots
not appliable

Desktop (please complete the following information):

OS: Linux Fedora
Architecture amd64
Version VSCode 1.117
Version VSCodium 1.135 (seen also here, initial report was about VSCodium 1.57)
App Manager RPM
Sandboxed NO

Additional context
Can be something related to Chromium or something related to VSCode/VSCodium
Browser often are distributed with some nasty settings OOB where they activate their own DNS settings ignoring the system. VSCode and VSCodium should force a better setup that respects the system settings as they are usually specific to the network environment.

https://github.com/VSCodium/vscodium/blob/master/docs/telemetry.md#update-services

Sorry, I was unable to reproduce this. Could you attempt launching VSCodium with codium --disable-extensions --user-data-dir /tmp/fresh --log-net-log=/tmp/netlog.json and see if you still get the dns stuff?

@lex-ibm

3. Sorry, I was unable to reproduce this. Could you attempt launching VSCodium with codium --disable-extensions --user-data-dir /tmp/fresh --log-net-log=/tmp/netlog.json and see if you still get the dns stuff?

Hi @lex-ibm
Yes, it is still the same.

From the firewall I see that it tries to contact dns.google.com even with the command you asked me

Hum, it seems that Electron need to be configured to use the system DNS...

const { app } = require('electron');

app.whenReady().then(() => {
  app.configureHostResolver({
    enableBuiltInResolver: false, // Disables Electron's internal resolver
    secureDnsMode: 'off'          // Disables DNS-over-HTTPS fallback
  });
});

electron/electron#49055

This needs to be looked into.

Navigation Menu

Repository navigation

VSCode/VSCodium not respecting network setup contacting directly dns.google.com #3058

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

VSCode/VSCodium not respecting network setup contacting directly dns.google.com #3058

Description

Activity

daiyam commented on Oct 9, 2026

lex-ibm commented on Oct 9, 2026

pasckosky commented on Oct 12, 2026

daiyam commented on Oct 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions