[GH-ISSUE #2655] AmneziaDNS is forced by the Windows client and also AmneziaDNS fails to resolve a lot of Russian domains

bsakaguchi commented

2026-10-13 20:36:50 +00:00

Owner

Originally created by @Stalinko on GitHub (May 26, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2655

Describe the bug
There are 2 bugs in 1:

AmneziaDNS is forced even when the AmneziaDNS is disabled in settings. You just turn on Amnezia Premium connection and the system DNS changes to 100.64.0.1
AmneziaDNS (specifically 100.64.0.1) fails to resolve plenty of Russian domain-names like e1.ru, e-kontur.ru etc. Just times out.

To Reproduce

Steps to reproduce the behavior:

Go to Amnezia VPN client on Windows
Ensure AmneziaDNS is disabled
Turn on VPN connection to Amnezia Premium (e.g. France)
Open the terminal and type "nslookup e1.ru"

Expected behavior
It resolves the domain

Actual behaviour

>nslookup e1.ru
Server:  UnKnown
Address:  100.64.0.1

DNS request timed out.
    timeout was 2 seconds.

Desktop (please complete the following information):

OS: Windows 11
Version 4.8.15.4

Additional context
Non-Russian domains resolve normally. E.g. google.com, github.com etc.

nslookup google.com
Server:  UnKnown
Address:  100.64.0.1

Не заслуживающий доверия ответ:
To :     google.com
Addresses:  192.178.183.113
          192.178.183.138
          192.178.183.139
          192.178.183.100
          192.178.183.101
          192.178.183.102

Originally created by @Stalinko on GitHub (May 26, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2655 **Describe the bug** There are 2 bugs in 1: 1. AmneziaDNS is forced even when the AmneziaDNS is disabled in settings. You just turn on Amnezia Premium connection and the system DNS changes to 100.64.0.1 2. AmneziaDNS (specifically 100.64.0.1) fails to resolve plenty of Russian domain-names like e1.ru, e-kontur.ru etc. Just times out. **To Reproduce** Steps to reproduce the behavior: 1. Go to Amnezia VPN client on Windows 2. Ensure AmneziaDNS is disabled 3. Turn on VPN connection to Amnezia Premium (e.g. France) 4. Open the terminal and type "nslookup e1.ru" **Expected behavior** It resolves the domain **Actual behaviour** ``` >nslookup e1.ru Server: UnKnown Address: 100.64.0.1 DNS request timed out. timeout was 2 seconds. ``` **Desktop (please complete the following information):** - OS: Windows 11 - Version 4.8.15.4 **Additional context** Non-Russian domains resolve normally. E.g. google.com, github.com etc. ``` nslookup google.com Server: UnKnown Address: 100.64.0.1 Не заслуживающий доверия ответ: To : google.com Addresses: 192.178.183.113 192.178.183.138 192.178.183.139 192.178.183.100 192.178.183.101 192.178.183.102 ````

bsakaguchi commented

2026-10-13 20:36:51 +00:00

Author

Owner

@Zettroke commented on GitHub (May 26, 2026):

Encountered this exact issue.
One interesting details is that even when explicitly specifying nslookup dns server it still times out.

command

> nslookup e1.ru 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to one.one.one.one timed-out

I tried to configure DNS in AmneziaVPN connection in windows settings (change 100.64.0.1 to 1.1.1.1 or 8.8.8.8), but it didn't work, still got timeouts.

One really terrible workaround is to hardcode IP addresses in your hosts file. Even though this is pretty bad solution, it worked for my employer's domains.

I'd really love to have more flexibility or at least more transparency in DNS shenanigans Amnezia is doing.

@Zettroke commented on GitHub (May 26, 2026): Encountered this exact issue. One interesting details is that even when explicitly specifying `nslookup` dns server it still times out. <details> <summary>command</summary> ``` > nslookup e1.ru 1.1.1.1 Server: one.one.one.one Address: 1.1.1.1 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to one.one.one.one timed-out ``` </details> I tried to configure DNS in `AmneziaVPN` connection in windows settings (change 100.64.0.1 to 1.1.1.1 or 8.8.8.8), but it didn't work, still got timeouts. <img width="886" height="409" alt="Image" src="https://github.com/user-attachments/assets/e03305a7-aca0-4d46-8a09-b470598446c6" /> One really terrible workaround is to hardcode IP addresses in your hosts file. Even though this is pretty bad solution, it worked for my employer's domains. I'd really love to have more flexibility or at least more transparency in DNS shenanigans `Amnezia` is doing.

bsakaguchi commented

2026-10-13 20:36:51 +00:00

Author

Owner

@Vitalik93 commented on GitHub (May 26, 2026):

Yes, same.

@Vitalik93 commented on GitHub (May 26, 2026): Yes, same.

bsakaguchi commented

2026-10-13 20:36:52 +00:00

Author

Owner

@MrShtein commented on GitHub (May 27, 2026):

The same

@MrShtein commented on GitHub (May 27, 2026): The same

bsakaguchi commented

2026-10-13 20:36:52 +00:00

Author

Owner

@yakimant commented on GitHub (May 28, 2026):

Looks duplicate for https://github.com/amnezia-vpn/amnezia-client/issues/1651

@yakimant commented on GitHub (May 28, 2026): Looks duplicate for https://github.com/amnezia-vpn/amnezia-client/issues/1651

bsakaguchi commented

2026-10-13 20:36:52 +00:00

Author

Owner

@Stalinko commented on GitHub (May 28, 2026):

@yakimant the problem here is wider. It could be okay to stay with AmneziaDNS if it worked flawlessly, but it breaks half of the internet.

@Stalinko commented on GitHub (May 28, 2026): @yakimant the problem here is wider. It could be okay to stay with AmneziaDNS if it worked flawlessly, but it breaks half of the internet.

bsakaguchi commented

2026-10-13 20:36:53 +00:00

Author

Owner

@alloploha commented on GitHub (May 29, 2026):

AmneziaDNS (specifically 100.64.0.1) fails to resolve plenty of Russian domain-names like e1.ru, e-kontur.ru etc. Just times out.

I’m pretty sure this is being done intentionally to protect VPN server IP addresses from being reported to Roskomnadzor by Russian websites and apps.

@alloploha commented on GitHub (May 29, 2026): >AmneziaDNS (specifically 100.64.0.1) fails to resolve plenty of Russian domain-names like e1.ru, e-kontur.ru etc. Just times out. I’m pretty sure this is being done intentionally to protect VPN server IP addresses from being reported to Roskomnadzor by Russian websites and apps.

bsakaguchi commented

2026-10-13 20:36:53 +00:00

Author

Owner

@Vitalik93 commented on GitHub (May 31, 2026):

На Финляндии причем открывается все русское нормально...

@Vitalik93 commented on GitHub (May 31, 2026): На Финляндии причем открывается все русское нормально...

bsakaguchi commented

2026-10-13 20:36:54 +00:00

Author

Owner

@yupic commented on GitHub (Jun 3, 2026):

Для браузера есть временное решение: не использовать системный DNS.

В настройках в поиске набрать "DNS", включить "Use secure DNS" и выбрать какого-нибудь провайдера, а не системный DNS.
Настройка есть в Chrome, Vivaldi и должна быть в других современных браузерах.

Но она может сломать что-то другое, с ней у меня нормально не грузится AI Studio.

@yupic commented on GitHub (Jun 3, 2026): Для браузера есть временное решение: не использовать системный DNS. <img width="994" height="503" alt="Image" src="https://github.com/user-attachments/assets/84f75505-b69e-4cd7-a01f-56c5fe7bc499" /> В настройках в поиске набрать "DNS", включить "Use secure DNS" и выбрать какого-нибудь провайдера, а не системный DNS. Настройка есть в Chrome, Vivaldi и должна быть в других современных браузерах. Но она может сломать что-то другое, с ней у меня нормально не грузится AI Studio.

bsakaguchi commented

2026-10-13 20:36:54 +00:00

Author

Owner

@Vitalik93 commented on GitHub (Jun 3, 2026):

Мне агент их поддержки помню сказал, что переключатель DNS в настройках работает только к self hosted. На Pemium получается он бесполезен, т.к. в любом случае будут встроенные DNS от Amnezia работать.

@Vitalik93 commented on GitHub (Jun 3, 2026): Мне агент их поддержки помню сказал, что переключатель DNS в настройках работает только к self hosted. На Pemium получается он бесполезен, т.к. в любом случае будут встроенные DNS от Amnezia работать.

bsakaguchi commented

2026-10-13 20:36:54 +00:00

Author

Owner

@corpro-friendee commented on GitHub (Jun 10, 2026):

I’m pretty sure this is being done intentionally to protect VPN server IP addresses from being reported ...

Мне агент их поддержки помню сказал, что переключатель DNS в настройках работает только к self hosted. На Pemium получается он бесполезен, т.к. в любом случае будут встроенные DNS от Amnezia работать.

Офигенная у вас квалификация конечно. The opposite side of the encounter is a bit stronger I suppose..

@corpro-friendee commented on GitHub (Jun 10, 2026): > I’m pretty sure this is being done intentionally to protect VPN server IP addresses from being reported ...   > Мне агент их поддержки помню сказал, что переключатель DNS в настройках работает только к self hosted. На Pemium получается он бесполезен, т.к. в любом случае будут встроенные DNS от Amnezia работать. Офигенная у вас квалификация конечно. The opposite side of the encounter is a bit stronger I suppose..

bsakaguchi commented

2026-10-13 20:36:54 +00:00

Author

Owner

@yakimant commented on GitHub (Jun 17, 2026):

It actually makes sense to enforce DNS and block all russian ips/sites on Premium/Free to make VPN ips safer.
But then it could be useful to show in UI.

@yakimant commented on GitHub (Jun 17, 2026): It actually makes sense to enforce DNS and block all russian ips/sites on Premium/Free to make VPN ips safer. But then it could be useful to show in UI.

bsakaguchi commented

2026-10-13 20:36:55 +00:00

Author

Owner

@Stalinko commented on GitHub (Jun 19, 2026):

Для браузера есть временное решение: не использовать системный DNS.

Unfortunately this doesn't work.
Amnezia blocks the DNS port, even "nslookup" with a custom DNS just doesn't pass through.

@Stalinko commented on GitHub (Jun 19, 2026): > Для браузера есть временное решение: не использовать системный DNS. Unfortunately this doesn't work. Amnezia blocks the DNS port, even "nslookup" with a custom DNS just doesn't pass through.

bsakaguchi commented

2026-10-13 20:36:55 +00:00

Author

Owner

@yupic commented on GitHub (Jun 19, 2026):

Для браузера есть временное решение: не использовать системный DNS.

Unfortunately this doesn't work. Amnezia blocks the DNS port, even "nslookup" with a custom DNS just doesn't pass through.

Chrome’s "Use secure DNS" setting uses DoH( DNS over HTTPS). It shouldn’t be affected by blocking the regular DNS port, because DoH is sent over HTTPS instead of port 53.

@yupic commented on GitHub (Jun 19, 2026): > > Для браузера есть временное решение: не использовать системный DNS. > > Unfortunately this doesn't work. Amnezia blocks the DNS port, even "nslookup" with a custom DNS just doesn't pass through. Chrome’s "Use secure DNS" setting uses DoH( DNS over HTTPS). It shouldn’t be affected by blocking the regular DNS port, because DoH is sent over HTTPS instead of port 53.

bsakaguchi commented

2026-10-13 20:36:55 +00:00

Author

Owner

@JayDi85 commented on GitHub (Aug 20, 2026):

Doesn't work on ru-domains and ru-sites

@JayDi85 commented on GitHub (Aug 20, 2026): Doesn't work on ru-domains and ru-sites

bsakaguchi referenced this issue

2026-10-13 21:20:26 +00:00

[PR #1208] [CLOSED] Issue 25 #2276

Rows
Columns

[GH-ISSUE #2655] AmneziaDNS is forced by the Windows client and also AmneziaDNS fails to resolve a lot of Russian domains #1208