trouble: DNS_PROBE_FINISHED_NXDOMAIN

[capibara2004]

When running any multizen profile without or with proxies, a DNS error occurs and the domain simply does not resolve. I believe the issue lies within the browser.

Additionally, I have noticed that requests to Russian-language websites are not functioning correctly.

# #

There is no problem on my end, I have tested it on similar octo/donut anti-detects, and they work perfectly
Please check and fix trouble

specs:
win 10 ltsc, local dns use

[jopthebot]

Thanks for the report — sorry you're hitting this.

I haven't been able to reproduce it on my side. I tested on macOS (CloakBrowser engine), both with and without a proxy, and DNS resolves fine, including Russian-language sites (checked yandex.ru, vk.com, ozon.ru, gosuslugi.ru — all load normally). So this doesn't look like a universal break; it seems specific to your environment (Win 10 LTSC + local DNS), which I can't see from here.

A couple of things worth knowing about how MultiZen handles DNS, so we can narrow it down:

• Without a proxy, MultiZen adds no DNS flags at all — it's the engine resolving via your system DNS directly. So a no-proxy NXDOMAIN points at the OS resolver / your local DNS setup or the engine on Windows, not at MultiZen's proxy handling.
• With a SOCKS5/HTTP proxy, DNS is resolved remotely by the proxy (the hostname is forwarded to it, not resolved locally). So if the proxy provider can't resolve a domain (or its exit is geo-blocked for .ru), you'd also see NXDOMAIN — but that's the upstream proxy, not local DNS.

To pin it down, could you share:

1. chrome://net-internals/#dns and #sockets captured right after the error (Export → attach the JSON, or screenshots).
2. Does it fail on a neutral domain like example.com, or only on specific (e.g. Russian) sites?
3. Direct (no proxy) vs with proxy — does it fail in both? If with-proxy: is it HTTP or SOCKS5, and does that same proxy resolve the same domain when you test it in plain Chrome / curl?
4. What exactly is your "local DNS" — AdGuard Home / Pi-hole / a corporate resolver / DoH enabled at the OS level?
5. MultiZen version (Help/About) and which engine you're on (System Chrome vs the bundled anti-detect engine).

With the net-internals capture I can tell immediately whether the resolution is failing locally or at the proxy. I'll also try to reproduce on a Win 10 LTSC VM in the meantime.

Appreciate the patience — let's get it sorted.