[GH-ISSUE #4364] DNS not working on IOS #8995

New Issue

@yurii-kysil commented on GitHub (Aug 19, 2025):

Same for me, but only using the wi-fi on iOS device (LTE is good):

example:

Also, no outbound messages could be sent over the internet (Slack, Teams, etc.) - maybe related to the same issue.

Also, attach the log:

netbird-log 2.txt

@yurii-kysil commented on GitHub (Aug 19, 2025): Same for me, but only using the wi-fi on iOS device (LTE is good): example: <img width="300" height="796" alt="Image" src="https://github.com/user-attachments/assets/d9e0bc8c-7c8a-4d11-a3dc-c783f9c7cf6d" /> <img width="300" height="796" alt="Image" src="https://github.com/user-attachments/assets/40e0b34f-2d4a-428b-8b95-6630bf95549a" /> Also, no outbound messages could be sent over the internet (Slack, Teams, etc.) - maybe related to the same issue. Also, attach the log: [netbird-log 2.txt](https://github.com/user-attachments/files/21850325/netbird-log.2.txt)

saavagebueno commented

@CodeShellDev commented on GitHub (Aug 22, 2025):

same here after moving the nameserver‘s ip…

Can ping the nameserver, but dns resolver isn't correctly set by Netbird in iOS. As a temporary workaround manually set resolver in Settings > Wifi > click (i) on connected Wifi > DNS > manual then add your nameserver's ip address manually.

@CodeShellDev commented on GitHub (Aug 22, 2025): same here after moving the nameserver‘s ip… Can ping the nameserver, but dns resolver isn't correctly set by Netbird in iOS. As a temporary workaround manually set resolver in Settings > Wifi > click (i) on connected Wifi > DNS > manual then add your nameserver's ip address manually.

saavagebueno commented

@stelle007 commented on GitHub (Aug 26, 2025):

Any news on this?

Anyone knows if it's only on selfhosted, or on clous setup aswell ?
on 5g it's not possible to eddit DNS by hand, it hase to be set by ISP or a VPN (netbird).

This renders Netbird unusable on Ios.

Is DNS working in Ios for anyone ?

@stelle007 commented on GitHub (Aug 26, 2025): Any news on this? Anyone knows if it's only on selfhosted, or on clous setup aswell ? on 5g it's not possible to eddit DNS by hand, it hase to be set by ISP or a VPN (netbird). This renders Netbird unusable on Ios. Is DNS working in Ios for anyone ?

saavagebueno commented

@slynetG commented on GitHub (Aug 30, 2025):

Same here. Was considering switching from tailscale to netbird, but this dns issue is a no go :(

@slynetG commented on GitHub (Aug 30, 2025): Same here. Was considering switching from tailscale to netbird, but this dns issue is a no go :(

saavagebueno commented

@stelle007 commented on GitHub (Sep 2, 2025):

Bump

@stelle007 commented on GitHub (Sep 2, 2025): Bump

saavagebueno commented

@xan-it commented on GitHub (Sep 18, 2025):

Same here on iOS 26 and iPadOS 26 with App Version 0.0.10.

@xan-it commented on GitHub (Sep 18, 2025): Same here on iOS 26 and iPadOS 26 with App Version 0.0.10.

saavagebueno commented

@troponaut commented on GitHub (Sep 20, 2025):

on iOS/iPadOS 26

running 0.0.10 (3) from TestFlight where the change log points to support for wildcard DNS routes.

Netbird DNS is being resolved correctly, and I am able to ping netbird IPs from my iPad.

Private DNS addresses routing configured in "Networks" resolve to the right IP address.

Wildcard DNS routing configured in "Networks" can't be resolved.

In this "Network" I also have routing peers routing to the full subnet, which also works great. I can ping that local subnet form my iPad.

@troponaut commented on GitHub (Sep 20, 2025): on iOS/iPadOS 26 running 0.0.10 (3) from TestFlight where the change log points to support for wildcard DNS routes. Netbird DNS is being resolved correctly, and I am able to ping netbird IPs from my iPad. Private DNS addresses routing configured in "Networks" resolve to the right IP address. Wildcard DNS routing configured in "Networks" can't be resolved. In this "Network" I also have routing peers routing to the full subnet, which also works great. I can ping that local subnet form my iPad.

saavagebueno commented

@CodeShellDev commented on GitHub (Sep 20, 2025):

So this has been resolved in 0.0.10? And is still not available on the App Store?

@CodeShellDev commented on GitHub (Sep 20, 2025): So this has been resolved in 0.0.10? And is still not available on the App Store?

saavagebueno commented

@troponaut commented on GitHub (Sep 20, 2025):

So this has been resolved in 0.0.10? And is still not available on the App Store?

Well wildcard DNS is not working on 0.0.10.

@troponaut commented on GitHub (Sep 20, 2025): > So this has been resolved in 0.0.10? And is still not available on the App Store? Well wildcard DNS is not working on 0.0.10.

saavagebueno commented

@Blacks-Army commented on GitHub (Oct 12, 2025):

I had the same problem, and the issue was that one device had Rosenpass disabled.

The problem was that Rosenpass-enabled devices can only communicate with other devices that also have Rosenpass enabled.

@Blacks-Army commented on GitHub (Oct 12, 2025): I had the same problem, and the issue was that one device had Rosenpass disabled. The problem was that Rosenpass-enabled devices can only communicate with other devices that also have Rosenpass enabled.

saavagebueno commented

@CodeShellDev commented on GitHub (Oct 12, 2025):

I had the same problem, and the issue was that one device had Rosenpass disabled.

The problem was that Rosenpass-enabled devices can only communicate with other devices that also have Rosenpass enabled.

For me communication works (+ DNS too), the issue is that the DNS settings aren't being applied in iOS, so you have to manually add the Nameserver to your DNS Servers (for each individual Wifi Network).

@CodeShellDev commented on GitHub (Oct 12, 2025): > I had the same problem, and the issue was that one device had Rosenpass disabled. > > The problem was that Rosenpass-enabled devices can only communicate with other devices that also have Rosenpass enabled. For me communication works (+ DNS too), the issue is that the DNS settings aren't being applied in iOS, so you have to manually add the Nameserver to your DNS Servers (for each individual Wifi Network).

saavagebueno commented

@Oujiii commented on GitHub (Oct 13, 2025):

Weird behaviour for me.

Works on my iPhone, but doesn't work on my iPad. It is weird because local DNS queries (for instance, accessing self hosted devices within my home) works pretty well. I can access jellyfin.mydomain.com, but if I try any domain that is out in the open, it doesn't work, but only on the iPad.

@Oujiii commented on GitHub (Oct 13, 2025): Weird behaviour for me. Works on my iPhone, but doesn't work on my iPad. It is weird because local DNS queries (for instance, accessing self hosted devices within my home) works pretty well. I can access jellyfin.mydomain.com, but if I try any domain that is out in the open, it doesn't work, but only on the iPad.

saavagebueno commented

@xan-it commented on GitHub (Oct 14, 2025):

updates to the iOS app version 0.0.11. Here I created a log file.
There are 2 interesting lines:

2025-10-13T20:42:21Z WARN client/internal/dns/upstream.go:254: probing upstream nameserver 192.168.200.18:53: with udp: read udp 192.168.1.210:63344->192.168.200.18:53: i/o timeout
2025-10-13T20:42:21Z INFO [nameservers: [{192.168.200.18 udp 53}]] client/internal/dns/server.go:830: Temporarily deactivating nameservers group due to timeout

When I manually check the dns on udp 53 on the same iOS device I can connect to the server.

@xan-it commented on GitHub (Oct 14, 2025): updates to the iOS app version 0.0.11. Here I created a log file. There are 2 interesting lines: ``` 2025-10-13T20:42:21Z WARN client/internal/dns/upstream.go:254: probing upstream nameserver 192.168.200.18:53: with udp: read udp 192.168.1.210:63344->192.168.200.18:53: i/o timeout 2025-10-13T20:42:21Z INFO [nameservers: [{192.168.200.18 udp 53}]] client/internal/dns/server.go:830: Temporarily deactivating nameservers group due to timeout ``` When I manually check the dns on udp 53 on the same iOS device I can connect to the server.

saavagebueno commented

@Raito00 commented on GitHub (Oct 26, 2025):

I’m experiencing the same problem, but only on iPhones.
My workaround was to install the Pi-hole Docker container on the same VM where the NetBird server is running, and then add it in the NetBird DNS settings (I’m using it only for exit nodes).

Now I also have a DNS filter option for exit nodes available, and there are no more DNS issues at all. 😊

@Raito00 commented on GitHub (Oct 26, 2025): I’m experiencing the same problem, but only on iPhones. My workaround was to install the Pi-hole Docker container on the same VM where the NetBird server is running, and then add it in the NetBird DNS settings (I’m using it only for exit nodes). Now I also have a DNS filter option for exit nodes available, and there are no more DNS issues at all. 😊

saavagebueno commented

@andycee commented on GitHub (Oct 31, 2025):

I’m experiencing the same problem, but only on iPhones. My workaround was to install the Pi-hole Docker container on the same VM where the NetBird server is running, and then add it in the NetBird DNS settings (I’m using it only for exit nodes).

Now I also have a DNS filter option for exit nodes available, and there are no more DNS issues at all. 😊

Please provide a bit more detail on this workaround. What IP addresses did you use for Pi-hole as a DNS in Netbird-UI?

@andycee commented on GitHub (Oct 31, 2025): > I’m experiencing the same problem, but only on iPhones. My workaround was to install the Pi-hole Docker container on the same VM where the NetBird server is running, and then add it in the NetBird DNS settings (I’m using it only for exit nodes). > > Now I also have a DNS filter option for exit nodes available, and there are no more DNS issues at all. 😊 Please provide a bit more detail on this workaround. What IP addresses did you use for Pi-hole as a DNS in Netbird-UI?

saavagebueno commented

@Raito00 commented on GitHub (Oct 31, 2025):

I run docker Pi-hole on the same VM where is netbird client. (i set in Pi-hole docker listen 5353:53)
Then In self hosted Netbird DNS-> Nameserver i add netbird VPN IP from VM where is Pi-hole IP:5353

@Raito00 commented on GitHub (Oct 31, 2025): I run docker Pi-hole on the same VM where is netbird client. (i set in Pi-hole docker listen 5353:53) Then In self hosted Netbird DNS-> Nameserver i add netbird VPN IP from VM where is Pi-hole IP:5353

saavagebueno commented

@laguilar21589 commented on GitHub (Jan 8, 2026):

I'm experiencing the same issue on iOS v0.60.9 with self-hosted Netbird.

Symptoms:

Network routing works perfectly (can access internal services via IP addresses using HTTP/SSH/RDP)
DNS configuration is received from Management server and visible in logs
Safari and Chrome cannot resolve internal domain names
Terminal apps (like iSH) CAN resolve domains using Netbird's internal resolver
The issue is specific to system-level DNS resolution in iOS

Root Cause (from debug logs):
DNS queries are being sent via the local WiFi interface instead of through the VPN tunnel:

read udp <local-wifi-ip>:<port>-><internal-dns-server>:53: i/o timeout

Expected behavior would be:

read udp <netbird-vpn-ip>:<port>-><internal-dns-server>:53

The VPN tunnel routes all other traffic correctly, but DNS queries specifically bypass it.

Workaround (unreliable):
Manual DNS configuration in iOS WiFi settings sometimes works:

Primary DNS: Internal DNS server IP
Secondary DNS: Public DNS (1.1.1.1 or 8.8.8.8)
Search Domain: internal.domain

However, this workaround:

Stops working randomly after reconnecting Netbird
Requires "tricks" to reactivate (changing secondary DNS or toggling airplane mode)
Only works on WiFi, not cellular data
iOS sometimes won't save the same configuration twice

Impact:
This makes iOS clients unreliable for accessing internal resources by hostname, forcing users to either:

Use IP addresses directly (not practical)
Use macOS/Windows/Linux/Android clients instead

This is a critical issue for mobile users needing access to internal infrastructure.

@laguilar21589 commented on GitHub (Jan 8, 2026): I'm experiencing the same issue on iOS v0.60.9 with self-hosted Netbird. **Symptoms:** - Network routing works perfectly (can access internal services via IP addresses using HTTP/SSH/RDP) - DNS configuration is received from Management server and visible in logs - Safari and Chrome cannot resolve internal domain names - Terminal apps (like iSH) CAN resolve domains using Netbird's internal resolver - The issue is specific to system-level DNS resolution in iOS **Root Cause (from debug logs):** DNS queries are being sent via the local WiFi interface instead of through the VPN tunnel: ``` read udp <local-wifi-ip>:<port>-><internal-dns-server>:53: i/o timeout ``` Expected behavior would be: ``` read udp <netbird-vpn-ip>:<port>-><internal-dns-server>:53 ``` The VPN tunnel routes all other traffic correctly, but DNS queries specifically bypass it. **Workaround (unreliable):** Manual DNS configuration in iOS WiFi settings sometimes works: - Primary DNS: Internal DNS server IP - Secondary DNS: Public DNS (1.1.1.1 or 8.8.8.8) - Search Domain: internal.domain However, this workaround: - Stops working randomly after reconnecting Netbird - Requires "tricks" to reactivate (changing secondary DNS or toggling airplane mode) - Only works on WiFi, not cellular data - iOS sometimes won't save the same configuration twice **Impact:** This makes iOS clients unreliable for accessing internal resources by hostname, forcing users to either: - Use IP addresses directly (not practical) - Use macOS/Windows/Linux/Android clients instead This is a critical issue for mobile users needing access to internal infrastructure.

saavagebueno commented

@Christopher87R commented on GitHub (Jan 12, 2026):

For me, it also doesn't work on iOS devices when I want to use an exit node.

@Christopher87R commented on GitHub (Jan 12, 2026): For me, it also doesn't work on iOS devices when I want to use an exit node.

saavagebueno commented

@ephb commented on GitHub (Jan 28, 2026):

Same issue, this renders NetBird unusable for my purposes.
Is this a regression or did this never fully work on iOS?

@ephb commented on GitHub (Jan 28, 2026): Same issue, this renders NetBird unusable for my purposes. Is this a regression or did this never fully work on iOS?

saavagebueno commented

@shuuri-labs commented on GitHub (Jan 29, 2026):

@Christopher87R @ephb @laguilar21589 @stelle007
could you please enable tracing logging in the app (under 'Advanced' in the sidebar menu) and share some logs here the next time you encouter this issue? would be very helpful in pinning it down :)

@shuuri-labs commented on GitHub (Jan 29, 2026): @Christopher87R @ephb @laguilar21589 @stelle007 could you please enable tracing logging in the app (under 'Advanced' in the sidebar menu) and share some logs here the next time you encouter this issue? would be very helpful in pinning it down :)

saavagebueno commented

@Christopher87R commented on GitHub (Jan 29, 2026):

netbird-log.txt

here you go

@Christopher87R commented on GitHub (Jan 29, 2026): [netbird-log.txt](https://github.com/user-attachments/files/24945733/netbird-log.txt) here you go

saavagebueno commented

netbird-app 2.log
netbird-app 3.log
netbird-app 6.16.44 p. m..log
netbird-app.log
netbird-engine 2.log
netbird-engine 3.log
netbird-engine 6.16.44 p. m..log
netbird-engine.log

@laguilar21589 commented on GitHub (Feb 3, 2026):

Ok, I have this logs.

@laguilar21589 commented on GitHub (Feb 3, 2026): [netbird-app 2.log](https://github.com/user-attachments/files/25051942/netbird-app.2.log) [netbird-app 3.log](https://github.com/user-attachments/files/25051936/netbird-app.3.log) [netbird-app 6.16.44 p. m..log](https://github.com/user-attachments/files/25051935/netbird-app.6.16.44.p.m.log) [netbird-app.log](https://github.com/user-attachments/files/25051941/netbird-app.log) [netbird-engine 2.log](https://github.com/user-attachments/files/25051937/netbird-engine.2.log) [netbird-engine 3.log](https://github.com/user-attachments/files/25051939/netbird-engine.3.log) [netbird-engine 6.16.44 p. m..log](https://github.com/user-attachments/files/25051940/netbird-engine.6.16.44.p.m.log) [netbird-engine.log](https://github.com/user-attachments/files/25051938/netbird-engine.log) Ok, I have this logs.

saavagebueno commented

@mlsmaycon commented on GitHub (Feb 8, 2026):

@laguilar21589 can you share more details on your dashboard configuration? Like which domain, what are the DNS settings, or routed DNS added.

@mlsmaycon commented on GitHub (Feb 8, 2026): @laguilar21589 can you share more details on your dashboard configuration? Like which domain, what are the DNS settings, or routed DNS added.

saavagebueno commented

@mlsmaycon commented on GitHub (Feb 8, 2026):

@laguilar21589 can you share more details on your dashboard configuration? Like which domain, what are the DNS settings, or routed DNS added.

nevermind, your previous message have all of that

@mlsmaycon commented on GitHub (Feb 8, 2026): > [@laguilar21589](https://github.com/laguilar21589) can you share more details on your dashboard configuration? Like which domain, what are the DNS settings, or routed DNS added. nevermind, your previous message have all of that

saavagebueno commented

@missingfile commented on GitHub (Mar 14, 2026):

This worked for me. https://www.reddit.com/r/netbird/comments/1rbrw39/comment/o6ymvvv/

@missingfile commented on GitHub (Mar 14, 2026): This worked for me. https://www.reddit.com/r/netbird/comments/1rbrw39/comment/o6ymvvv/

saavagebueno commented

@lixmal commented on GitHub (Apr 8, 2026):

This has been addressed across multiple releases:

#5694 (v0.67.1): replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route checker
#5802 (v0.67.4): fixed DNS route check for deselected exit nodes
#5803 (v0.68.0): fixed iOS DNS upstream routing so deselected exit nodes no longer block resolver switching

If you're still experiencing iOS DNS issues, please test with iOS client v0.1.4 (available via TestFlight) and report back.

@lixmal commented on GitHub (Apr 8, 2026): This has been addressed across multiple releases: - #5694 (v0.67.1): replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route checker - #5802 (v0.67.4): fixed DNS route check for deselected exit nodes - #5803 (v0.68.0): fixed iOS DNS upstream routing so deselected exit nodes no longer block resolver switching If you're still experiencing iOS DNS issues, please test with iOS client v0.1.4 (available via TestFlight) and report back.

saavagebueno commented

@stelle007 commented on GitHub (Apr 8, 2026):

I have joined testflight, bu I only see v 0.1.3 (36) as the latest. and
with that version I still have the issue.

On Wed, 8 Apr 2026 at 11:53, Viktor Liu @.***> wrote:

lixmal left a comment (netbirdio/netbird#4364)
https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461

This has been addressed across multiple releases:

#5694 https://github.com/netbirdio/netbird/pull/5694 (v0.67.1):
replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route
checker

#5802 https://github.com/netbirdio/netbird/pull/5802 (v0.67.4):
fixed DNS route check for deselected exit nodes

#5803 https://github.com/netbirdio/netbird/pull/5803 (v0.68.0):
fixed iOS DNS upstream routing so deselected exit nodes no longer block
resolver switching

If you're still experiencing iOS DNS issues, please test with iOS client
v0.1.4 (available via TestFlight) and report back.

—
Reply to this email directly, view it on GitHub
https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXFZKI3WQE3AWIA3WIFIXTL4UYOSPAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBVGM4DGNBWGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Steffen Ørskov
@.***

@stelle007 commented on GitHub (Apr 8, 2026): I have joined testflight, bu I only see v 0.1.3 (36) as the latest. and with that version I still have the issue. On Wed, 8 Apr 2026 at 11:53, Viktor Liu ***@***.***> wrote: > *lixmal* left a comment (netbirdio/netbird#4364) > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461> > > This has been addressed across multiple releases: > > - #5694 <https://github.com/netbirdio/netbird/pull/5694> (v0.67.1): > replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route > checker > - #5802 <https://github.com/netbirdio/netbird/pull/5802> (v0.67.4): > fixed DNS route check for deselected exit nodes > - #5803 <https://github.com/netbirdio/netbird/pull/5803> (v0.68.0): > fixed iOS DNS upstream routing so deselected exit nodes no longer block > resolver switching > > If you're still experiencing iOS DNS issues, please test with iOS client > v0.1.4 (available via TestFlight) and report back. > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXFZKI3WQE3AWIA3WIFIXTL4UYOSPAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBVGM4DGNBWGE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Steffen Ørskov ***@***.***

saavagebueno commented

@jfrconley commented on GitHub (Apr 13, 2026):

I have joined testflight, bu I only see v 0.1.3 (36) as the latest. and

with that version I still have the issue.

On Wed, 8 Apr 2026 at 11:53, Viktor Liu @.***> wrote:

lixmal left a comment (netbirdio/netbird#4364)

https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461

This has been addressed across multiple releases:

#5694 https://github.com/netbirdio/netbird/pull/5694 (v0.67.1):

replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route

checker

#5802 https://github.com/netbirdio/netbird/pull/5802 (v0.67.4):

fixed DNS route check for deselected exit nodes

#5803 https://github.com/netbirdio/netbird/pull/5803 (v0.68.0):

fixed iOS DNS upstream routing so deselected exit nodes no longer block

resolver switching

If you're still experiencing iOS DNS issues, please test with iOS client

v0.1.4 (available via TestFlight) and report back.

—

Reply to this email directly, view it on GitHub

https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/AXFZKI3WQE3AWIA3WIFIXTL4UYOSPAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBVGM4DGNBWGE

.

You are receiving this because you were mentioned.Message ID:

@.***>

--

Steffen Ørskov

@.***

Same for me currently, only O.1.3 (36) available. DNS works for a while, but will stop responding after network changes

@jfrconley commented on GitHub (Apr 13, 2026): > I have joined testflight, bu I only see v 0.1.3 (36) as the latest. and > > with that version I still have the issue. > > > > On Wed, 8 Apr 2026 at 11:53, Viktor Liu ***@***.***> wrote: > > > > > *lixmal* left a comment (netbirdio/netbird#4364) > > > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461> > > > > > > This has been addressed across multiple releases: > > > > > > - #5694 <https://github.com/netbirdio/netbird/pull/5694> (v0.67.1): > > > replaced the IsPrivate heuristic in iOS DNS upstream resolver with a route > > > checker > > > - #5802 <https://github.com/netbirdio/netbird/pull/5802> (v0.67.4): > > > fixed DNS route check for deselected exit nodes > > > - #5803 <https://github.com/netbirdio/netbird/pull/5803> (v0.68.0): > > > fixed iOS DNS upstream routing so deselected exit nodes no longer block > > > resolver switching > > > > > > If you're still experiencing iOS DNS issues, please test with iOS client > > > v0.1.4 (available via TestFlight) and report back. > > > > > > — > > > Reply to this email directly, view it on GitHub > > > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4205383461>, > > > or unsubscribe > > > <https://github.com/notifications/unsubscribe-auth/AXFZKI3WQE3AWIA3WIFIXTL4UYOSPAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBVGM4DGNBWGE> > > > . > > > You are receiving this because you were mentioned.Message ID: > > > ***@***.***> > > > > > > > > > -- > > Steffen Ørskov > > ***@***.*** > > Same for me currently, only O.1.3 (36) available. DNS works for a while, but will stop responding after network changes

saavagebueno commented

@Blacks-Army commented on GitHub (Apr 13, 2026):

0.1.4 is on the AppStore

@Blacks-Army commented on GitHub (Apr 13, 2026): 0.1.4 is on the AppStore

saavagebueno commented

@stelle007 commented on GitHub (Apr 13, 2026):

That did it, it now works for me.

On Mon, 13 Apr 2026 at 10:02, Mustafa @.***> wrote:

Blacks-Army left a comment (netbirdio/netbird#4364)
https://github.com/netbirdio/netbird/issues/4364#issuecomment-4234758560

0.1.4 is on the AppStore

—
Reply to this email directly, view it on GitHub
https://github.com/netbirdio/netbird/issues/4364#issuecomment-4234758560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXFZKI2LVALUI3KZCFXZBHD4VSNJVAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZUG42TQNJWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Steffen Ørskov
@.***

@stelle007 commented on GitHub (Apr 13, 2026): That did it, it now works for me. On Mon, 13 Apr 2026 at 10:02, Mustafa ***@***.***> wrote: > *Blacks-Army* left a comment (netbirdio/netbird#4364) > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4234758560> > > 0.1.4 is on the AppStore > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbirdio/netbird/issues/4364#issuecomment-4234758560>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXFZKI2LVALUI3KZCFXZBHD4VSNJVAVCNFSM6AAAAACEFDPMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZUG42TQNJWGA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Steffen Ørskov ***@***.***

saavagebueno commented

@mi7chal commented on GitHub (Apr 22, 2026):

For me this issue persists. Version 0.68.3 on IOS 26.4.1. No internal domain can be resolved. Connecting directly to IPs works or resolving public domains works tho. I use the Netbird Free Plan with only one name server matching only one specific domain.

@mi7chal commented on GitHub (Apr 22, 2026): For me this issue persists. Version `0.68.3` on `IOS 26.4.1`. No internal domain can be resolved. Connecting directly to IPs works or resolving public domains works tho. I use the Netbird Free Plan with only one name server matching only one specific domain.

saavagebueno commented

@ephb commented on GitHub (Apr 23, 2026):

@mi7chal I had to reboot and toggle VPN off and on when this occurred for me and now it has not broken in a while.

@ephb commented on GitHub (Apr 23, 2026): @mi7chal I had to reboot and toggle VPN off and on when this occurred for me and now it has not broken in a while.

saavagebueno commented

@mi7chal commented on GitHub (Apr 24, 2026):

Unfortunately no changes after reboot or turning on/off for me.

@mi7chal commented on GitHub (Apr 24, 2026): Unfortunately no changes after reboot or turning on/off for me.

saavagebueno commented

@techfoxactual commented on GitHub (May 3, 2026):

No DNS for me, iOS 26.4.2, App says it is v0.1.5, as soon as I enable Netbird all DNS is totally killed.

EDIT I found if I specified Local DNS servers on my Netbird controller by giving my DNS servers netbird addresses, they propagated to and were used by the iOS device. So it is the act of not setting up Local DNS servers within netbird that seems to just clobber any iOS DNS settings and resolve nothing.

TL;DR not setting up Local DNS server in Netbird = Zero DNS resolution on iOS.

@techfoxactual commented on GitHub (May 3, 2026): No DNS for me, iOS 26.4.2, App says it is v0.1.5, as soon as I enable Netbird all DNS is totally killed. **EDIT** I found if I specified Local DNS servers on my Netbird controller by giving my DNS servers netbird addresses, they propagated to and were used by the iOS device. So it is the act of not setting up Local DNS servers within netbird that seems to just clobber any iOS DNS settings and resolve nothing. TL;DR not setting up Local DNS server in Netbird = Zero DNS resolution on iOS. <img width="1503" height="180" alt="Image" src="https://github.com/user-attachments/assets/78dc10c5-323c-4e81-bfa5-a57be634833b" />

saavagebueno commented

@mitchplze commented on GitHub (May 17, 2026):

TL;DR not setting up Local DNS server in Netbird = Zero DNS resolution on iOS.

I believe this same issue exists also on macOS (possibly others). I saw it the other day. If you don’t define “some” kind of arbitrary nameserver, you get no DNS resolution, even for your NetBird domain FQDN.

@mitchplze commented on GitHub (May 17, 2026): > TL;DR not setting up Local DNS server in Netbird = Zero DNS resolution on iOS. I believe this same issue exists also on macOS (possibly others). I saw it the other day. If you don’t define “some” kind of arbitrary nameserver, you get no DNS resolution, even for your NetBird domain FQDN.

saavagebueno commented

@sbrandsen commented on GitHub (Jun 2, 2026):

This issue still persists, and prevents me from switching fully to Netbird. Hope there is a solution soon!

@sbrandsen commented on GitHub (Jun 2, 2026): This issue still persists, and prevents me from switching fully to Netbird. Hope there is a solution soon!

saavagebueno commented

@joachimtingvold commented on GitHub (Jun 7, 2026):

I have a similar issue. Coming from #4386, where I had to set "Groups: All" for DNS to work at all on my iPhone. After removing Netbird from my iPhone, and re-adding it, at least it now resolves. However, it's VERY slow. Takes probably 5 seconds to resolve a domain via the x.x.x.254 internal NetBird resolver. Switching to use the DNS-server IP directly (reachable via the VPN), it resolves instantly. This is with latest Netbird-server (0.72.2) and iOS client (0.2.0).

Maybe an option to set the defined DNS-servers directly would solve a lot of problems? (i.e. bypass the x.x.x.254 internal NetBird DNS logic). For those of us who don't need the "DNS Zones" functionality, or "per zone name servers" (i.e. we only use the "Match domains: ALL" default setting).

edit: upgrading to the TestFlight-version (0.2.1 build 19) solved the "slow DNS" issue for me on my iPhone.

@joachimtingvold commented on GitHub (Jun 7, 2026): I have a similar issue. Coming from #4386, where I had to set "Groups: All" for DNS to work at all on my iPhone. After removing Netbird from my iPhone, and re-adding it, at least it now resolves. However, it's VERY slow. Takes probably 5 seconds to resolve a domain via the x.x.x.254 internal NetBird resolver. Switching to use the DNS-server IP directly (reachable via the VPN), it resolves instantly. This is with latest Netbird-server (0.72.2) and iOS client (0.2.0). Maybe an option to set the defined DNS-servers directly would solve a lot of problems? (i.e. bypass the x.x.x.254 internal NetBird DNS logic). For those of us who don't need the "DNS Zones" functionality, or "per zone name servers" (i.e. we only use the "Match domains: ALL" default setting). edit: upgrading to the TestFlight-version (0.2.1 build 19) solved the "slow DNS" issue for me on my iPhone.

saavagebueno commented