Big Sur DNS Issue

Hi,

Since updating to Big Sur i've had this strange error, that i've been debugging to try and help out a bit with this error i'm getting with local DNS.

I use Docker/Kubernetes locally to run a particular application at a series of particular domains via the browser. I do this by adding local IPs to the Network/(Adapter)/DNS/DNS Servers and having the last item be 8.8.8.8 so it would pick up the local docker container DNS first and fall back etc.

Upon upgrading (from Catalina) I noticed that these were not working.
so did the normal things of flushing DNS, clearing cache etc. Then it would work, but only for a small period of time after a DNS flush using:

Code Block 
sudo killall -HUP mDNSResponder

So i would have a small window where i could access these, and once on the domain it seemed to be fine and would stick the DNS to the correct DNS Server IP, however all other local domains would fail, but if i run the flush DNS command again it would allow me onto the failed domain again.

I naturally debugged all my containers and they are working as intended as seen via the fact they're responding correctly some of the time, but as it requires a DNS flush it seems like there is more of an issue there.

Has anyone else had any issues using DNS servers, and does anyone have an advice for maybe debugging this further?

Thanks!
Up vote post of mdsmash Down vote post of mdsmash
8.9k views
Posted by
mdsmash
Reply
Add a Comment

Replies

I'm having DNS issues in macOS Big Sur. I described the issues here: https://developer.apple.com/forums/thread/670856
Posted by
shoelzle
Up vote reply of shoelzle Down vote reply of shoelzle
Add a Comment
Updates should NEVER break DNS!!!
Posted by
Ike443
Up vote reply of Ike443 Down vote reply of Ike443
Add a Comment

I have this issue with the latest Cisco Anyconnect & Big Sur update as of 2021-07-19.

For me, the sudo killall -HUP mDNSResponder is inconsistent and works only for a few minutes. A better solution for me is to use Google (or cloudflare DNS) servers.

  1. Go to Settings -> Network -> Advanced -> DNS tab
  2. Click '+', then add server 8.8.8.8
  3. Delete any other DNS servers in this list by selecting them and pressing '-' (minus)
  4. Click OK, then Apply, then restart.

I haven't encountered any problems with this approach so far.

Posted by
augustnagro
Post not yet marked as solved Up vote reply of augustnagro Down vote reply of augustnagro

  • I bet if one goes right step 4 part 3 and just "restart" the problem will be fixed without doing anything else. In fact, that's exactly what I do when DNS stops working: just reboot. If anybody knows how to get DNS going again WITHOUT a reboot, I'm all ears.

    It's a bit comical how so many "solutions" include elaborate instructions only to end with "reboot"! "dscacheutil, then stand one left leg and swing arms in big circles from North to South while singing the national anthem of your choice at half volume then.... restart'!

    —
    aqn

  • Absolutely same for me. Nothing help except a reboot. This is very annoying. MacBook Pro 16, M1 Max, macOS Monterey 12.1. Also using Cisco AnyConnect.

    —
    Fire7
Add a Comment