[GH-ISSUE #1841] MacOS Amnezia VPN client Ignores system-wide search-domain #788

New issue

Open

opened 2026-10-13 20:28:35 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-13 20:28:35 +00:00

Owner

Originally created by @rmdevheart on GitHub (Sep 5, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1841

At the system level, search-domain is set:

networksetup -getsearchdomains Wi-Fi
mydomain.io

however, when an AmneziaVPN client connected, it is ignored and the request for a short hostname (nslookup server1) comes to the DNS server like:

13:42:27.981870 awg_clients In IP 10.78.100.3.60836 > 10.78.100.1.53: 32716+ A? server1.lan. (26)
13:42:28.051622 awg_clients In IP 10.78.100.3.52900 > 10.78.100.1.53: 36921+ A? server1. (22)

It is expected that the A-query should receive a request for server1.mydomain.io.

It has been noted that if search-domain is not specified in the systemwide settings, but is passed via dhcp-option from the router,

ipconfig getpacket en0 
op = BOOTREPLY
options:
domain_search (dns_namelist): {mydomain.io}

then the same operation works correctly

13:47:37.537974 awg_clients In IP 10.78.100.3.61822 > 10.78.100.1.53: 36556+ A? server1.mydomain.io. (40)
13:47:37.542665 awg_clients Out IP 10.78.100.1.53 > 10.78.100.3.61822: 36556 1/0/0 A 10.78.4.80 (56)

Originally created by @rmdevheart on GitHub (Sep 5, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1841 At the system level, search-domain is set: ``` networksetup -getsearchdomains Wi-Fi mydomain.io ``` however, when an AmneziaVPN client connected, it is ignored and the request for a short hostname (nslookup server1) comes to the DNS server like: ``` 13:42:27.981870 awg_clients In IP 10.78.100.3.60836 > 10.78.100.1.53: 32716+ A? server1.lan. (26) 13:42:28.051622 awg_clients In IP 10.78.100.3.52900 > 10.78.100.1.53: 36921+ A? server1. (22) ``` It is expected that the A-query should receive a request for server1.mydomain.io. It has been noted that if search-domain is not specified in the systemwide settings, but is passed via dhcp-option from the router, ``` ipconfig getpacket en0 op = BOOTREPLY options: domain_search (dns_namelist): {mydomain.io} ``` then the same operation works correctly ``` 13:47:37.537974 awg_clients In IP 10.78.100.3.61822 > 10.78.100.1.53: 36556+ A? server1.mydomain.io. (40) 13:47:37.542665 awg_clients Out IP 10.78.100.1.53 > 10.78.100.3.61822: 36556 1/0/0 A 10.78.4.80 (56) ```

bsakaguchi commented

2026-10-13 20:28:37 +00:00

Author

Owner

@rmdevheart commented on GitHub (Sep 5, 2025):

Update:

When client connected, /etc/resolv.conf is modified and this explain all behaviour above

search lan
nameserver {IP from client settings}

Looks like it need to be fixed with system search-domain here >> https://github.com/amnezia-vpn/amnezia-client/blob/dev/deploy/data/macos/update-resolv-conf.sh

@rmdevheart commented on GitHub (Sep 5, 2025): Update: When client connected, /etc/resolv.conf is modified and this explain all behaviour above ``` search lan nameserver {IP from client settings} ``` Looks like it need to be fixed with system search-domain here >> https://github.com/amnezia-vpn/amnezia-client/blob/dev/deploy/data/macos/update-resolv-conf.sh

bsakaguchi referenced this issue

2026-10-13 21:18:41 +00:00

[PR #788] [MERGED] Invert received/sent data for client info #2112