[GH-ISSUE #2993] [macOS][Self-Hosted][XRay] DNS fails only when Use AmneziaDNS is enabled #1373

Open
opened 2026-10-13 20:41:07 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @AlexCawl on GitHub (Aug 16, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2993

Describe the bug
On macOS, DNS resolution stops working when Use AmneziaDNS is enabled for a self-hosted XRay connection. The app reports Connected, and fixed-IP HTTPS works through the VPS. Disabling only AmneziaDNS restores DNS while XRay remains active.

To Reproduce

  1. Connect to self-hosted XRay VLESS/REALITY in full-tunnel mode.
  2. Enable Use AmneziaDNS.
  3. Observe that websites do not resolve.
  4. Run dig +time=3 +tries=1 @1.1.1.1 google.com and dig +tcp +time=3 +tries=1 @1.1.1.1 google.com; both time out.
  5. Disable only Use AmneziaDNS and reconnect.
  6. Repeat the UDP query; it succeeds, and curl -4 https://api.ipify.org still returns the VPS exit IP.

Expected behavior
DNS resolution should work while AmneziaDNS is enabled.

Log files
Not attached.

Screenshots
Not applicable.

Desktop:

  • OS: macOS 15.7.7, arm64
  • Version: AmneziaVPN 5.0.0.5

Smartphone:

  • Not tested

Server:

  • OS: Ubuntu 24.04.4 LTS

Additional context
No server configuration or split-tunnel exclusions were changed. Related to #2896, but in this case disabling AmneziaDNS alone is sufficient: public DNS works through the XRay tunnel without exclusions.

Originally created by @AlexCawl on GitHub (Aug 16, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2993 **Describe the bug** On macOS, DNS resolution stops working when **Use AmneziaDNS** is enabled for a self-hosted XRay connection. The app reports **Connected**, and fixed-IP HTTPS works through the VPS. Disabling only AmneziaDNS restores DNS while XRay remains active. **To Reproduce** 1. Connect to self-hosted XRay VLESS/REALITY in full-tunnel mode. 2. Enable **Use AmneziaDNS**. 3. Observe that websites do not resolve. 4. Run `dig +time=3 +tries=1 @1.1.1.1 google.com` and `dig +tcp +time=3 +tries=1 @1.1.1.1 google.com`; both time out. 5. Disable only **Use AmneziaDNS** and reconnect. 6. Repeat the UDP query; it succeeds, and `curl -4 https://api.ipify.org` still returns the VPS exit IP. **Expected behavior** DNS resolution should work while AmneziaDNS is enabled. **Log files** Not attached. **Screenshots** Not applicable. **Desktop:** - OS: macOS 15.7.7, arm64 - Version: AmneziaVPN 5.0.0.5 **Smartphone:** - Not tested **Server:** - OS: Ubuntu 24.04.4 LTS **Additional context** No server configuration or split-tunnel exclusions were changed. Related to #2896, but in this case disabling AmneziaDNS alone is sufficient: public DNS works through the XRay tunnel without exclusions.
Author
Owner

@Vitalik93 commented on GitHub (Aug 17, 2026):

Странно. У меня на self hosted тоже стоит их DNS (используют Cloudflare) и работает нормально.

<!-- gh-comment-id:5318492805 --> @Vitalik93 commented on GitHub (Aug 17, 2026): Странно. У меня на self hosted тоже стоит их DNS (используют Cloudflare) и работает нормально.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
amnezia-vpn/amnezia-client#1373
No description provided.