Apple Intelligence now features Image Playground, Genmoji, Writing Tools enhancements, seamless support for ChatGPT, and visual intelligence.

Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >

You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

hamacardo Author

Level 1

31 points

VPN / DNS Issues With macOS Ventura

After upgrading MacBook Air M1 to Ventura I noticed that several of our internal business sites, RDP connections and Network SMB folders which require a VPN to access would not resolve, even after a successful VPN connection. and would only work via their respective IP addresses

Usual troubleshooting including...

Home router reboots
Mac reboots
Re-creating VPN connection
Different browsers
Different VPN account
macOS DNS cache clear
Switching to a mobile data (tethered) connection and then connecting to the vpn did not resolve

In desperation had to resort to manually editing the HOSTS file

sudo nano /etc/hosts

... which allowed the respective sites, folders and connections to resolve.

It's clear that Apple devs have broken DNS networking stuff which worked in Monterey and before.

Users should not have to manually edit the macOS HOSTS file to use DNS names whilst connected to a VPN in Ventura

MacBook Air 13″, macOS 13.0

Posted on Oct 26, 2022 5:48 PM

Top-ranking reply

f1r3s4l3

Level 1

30 points

Posted on Dec 16, 2022 7:38 AM

To put it very simply: This is a very normal feature, and it worked in 12.x but does not correctly in 13.x.

And as it (at leas in my case) only happens after the device went to sleep, it would seem common sense that it's not working as designed.

So IMHO it's quite irrelevant whether we're using this to connect to our VPN at home but still want a public DNS for whatever reasons, or if we're stumbling upon this issue in an enterprise environment.

Apple should be grateful that we're bringing this to the public and thus helping to improve their products, but if they prefer to not talk about any potential issues, well...

I find it quite funny that every time someone finds a bug or something like that in an Apple product, someone with thousands of points jumps in to defend Apple. And I wonder if this comment will even make it to the forum, as my last try at a reply was censored for reasons unknown.

View in context

Similar questions

89 replies

ibgb

Level 1

54 points

Mar 23, 2024 3:26 PM in response to hamacardo

Some dns servers encrypt their conversations, like 1.1.1.1. Some non-encrypted dns servers do not so it is all readable to whomever. Maybe when one selects do not track or limit IP tracking macos will prefer encrypted dns conversations and override using a local non-encrypted dns server because of the limit IP tracking request.

Apr 26, 2024 6:22 AM in response to hamacardo

Hi guys,

I still have similar issues with Sonoma 14.4.1. on Macbooks 18,2.

However, I only added 3 internal DNS servers and 3 internal search domains in the wired and Wi-Fi network configurations. We aren't using any external DNS servers, so the workarounds in this thread aren't solutions for us. And like others mentioned, all worked fine in previous macOS version (Monterey, Big Sur, Mojave, High Sierra...).

Another annoying fact about Ventura/Sonoma, you can't enable Apple Remote Desktop with scripts using MDM. You can only enable it directly on the computer.

Que Apple sera, sera.

May 3, 2024 5:00 AM in response to peterwilson_69

Just a quick update; my Mac has an Intel CPU so I used BootCamp to install Windows 10 on it - and honestly wish I had done so earlier. I feel like I have a brand new modern laptop, with awesome battery life! I was so impressed I converted my wife’s too (at her request), and one of my best mates is upset because he doesn’t have the Intel CPU in his MacBook Air. Best of luck everyone.

f1r3s4l3

Level 1

30 points

May 11, 2024 12:50 PM in response to lequi

What issue? Everything is working as expected/designed. <sarcasm off/>

Seriously, don't expect them to resolve this at all. We've resorted to fixing DNS to a nameserver behind the VPN and force the VPN connection on login.

Old Toad

Level 10

210,795 points

Apr 4, 2023 2:45 PM in response to hamacardo

Along with what abitgroggy said you might try using the Open DNS servers:

208.67.222.222

208.67.220.220

Oct 27, 2022 11:38 PM in response to abitgroggy

The same here, MacMini studio after the upgrade to Ventura the internal DNS names are not resolved.

Stopping and starting Wifi helps but only for a short time.

Oct 29, 2022 5:16 PM in response to abitgroggy

And if 1.1.1.1 is the secondary in the /etc/resolver file, the behavior is again failure...

f1r3s4l3

Level 1

30 points

Nov 1, 2022 6:03 AM in response to f1r3s4l3

After several sleep/wake-cycles I can confirm that after removing 8.8.8.8 from the DNS servers in the network settings, the issue is gone.

Nov 11, 2022 5:18 PM in response to OverweightBatman

Wondering if anyone testing 13.1 has noted this being fixed or not?

Nov 14, 2022 7:52 AM in response to abitgroggy

I updated one of our Mac Books to 13.1 and so far, I have not been experiencing the same issues. Initially it seems as though the issue has been fixed.

Dec 14, 2022 12:45 PM in response to OverweightBatman

I've upgraded to 13.1 today as well, still an issue for me.

etresoft

Level 9

51,442 points

Dec 15, 2022 2:11 PM in response to abitgroggy

Why would anyone want to use a VPN with a public DNS? Doesn't that kind of defeat the purpose?

Dec 16, 2022 2:49 AM in response to f1r3s4l3

Moreover, you want to use company DNS only while connected to VPN but still have a fallback for when it's not reachable.

Dec 24, 2022 9:08 AM in response to hamacardo

Same experience. I have downgraded to Monterey 12.6.2 and will stay there until this is resolved.

dcarrera

Level 1

8 points

Jan 9, 2023 6:34 AM in response to hamacardo

Same situation here, with or without VPN. Running Ventura 13.1 and can only have one DNS server listed for my resolver - otherwise DNS resolution is not working at all...

VPN / DNS Issues With macOS Ventura