MacBook cannot do DNS lookup after waking up from sleep

I am having the same issue on 16" MacBook Pro M2 Max running Ventura 13.4.1. After waking from sleep, only specific domains aren't able to be resolved. slack is one of them. I have tried using 1.1.1.1 and 8.8.8.8 for DNS. The only thing that fixes it is restarting the machine.

vamfoom wrote:

For the past week, my MacBook has been refusing to do DNS lookups unless it’s rebooted. The machine is running Ventura 13.4 and I am able to ping every system on my local network.

The /etc/resolv.conf file appears to be correct. In an attempt to resolve the issue, I have flushed the DNS cache and restarted/reloaded mDNSResponder with no success.

The only solution that seems to work is rebooting the machine. Do you have any other ideas on how to fix this issue?

Look if there is more here...

see Bob Harris:

macbook pro upgrade to ventura 13.3.1 - Apple Community

Symptoms in my case

• waking up the machine from a longer sleep, network connection is broken on all wifi networks (haven't tried wired or mobile hotspots) (I have Ventura 13.5.2 on M1 Pro)
• ping 'google.com' unresponsive
• ping any IP address, works
• I've been observing crashes with some delay after problem onset:

panic(cpu 1 caller 0xfffffe0013cf6e58): userspace watchdog timeout: no successful checkins from configd in 180 seconds
configd has not exited since first loaded
service: logd, total successful checkins in 46119 seconds: 4440, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 46063 seconds: 4436, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 46119 seconds: 4421, last successful checkin: 180 seconds ago

• restart solves the issues

Tried and didn't work

• reconnecting wifi,
• sleep-wake cycle,
• wifi disable-enable cycle,
• updating dns server address

Next to try:

• I faintly recall that nslookup is using the system builtin modules, whereas dig has it's own, so I'll compare nslookup, dig and maybe other DNS lookup utilities to isolate the issue and verify it is really it the system dns resolution
• Given configd is also (indirectly?) responsible for DNS resolution, I'll dig deeper if the error occurs again.

This is nightmare… Tried restarting services using Terminal, but nothing on the internet helps… tired of rebooting that Macbook…

Was anyone able to figure out this problem. I have had the same issue for quite a while now. It does work when I connect to my phone hotspot, so I am wondering if it has to do with my wifi router.

The way I was able to “fix” this is by deleting the WiFi adapter in Settings > Network and then Re-Adding it. This solved the issue for me and has not happened since.

I hope this helps.

Thank you for that suggestion. I removed/re-added my Thunderbolt Hub, and my connection seems to be working now