Basic DNSResolver dropping message because it doesn’t match the one sent Port:0 – my fix

I have lots of probably horrible habits, but one is dropping into the Console to look at the system log every now and then.

A few days ago I did so, for the first time in weeks, to find literally tens of thousands of these:

Nov 8 12:33:42 myQuad.local discoveryd[56]: Basic DNSResolver dropping message because it doesn’t match the one sent Port:0 MsgID:13367
Nov 8 12:33:42 myQuad.local discoveryd[56]: Basic DNSResolver dropping message because it doesn’t match the one sent Port:0 MsgID:14649
Nov 8 12:33:42 myQuad.local discoveryd[56]: Basic DNSResolver dropping message because it doesn’t match the one sent Port:0 MsgID:12295
Nov 8 12:33:42 myQuad.local discoveryd[56]: Basic DNSResolver dropping message because it doesn’t match the one sent Port:0 MsgID:28005

That, in turn, lead to a search of the web, where it seems to be not completely uncommon. And LOTS of things to try to fix it. I tried a few, and in the process corrupted my drive, leading to dozens of hours of testing, repair, re-installs, more research and so on .

Port zero is a “non-port” sometimes used to get the OS to seach for and supply a free port. What that tells me is that whatever was causing these entries was local. My Synology? My network tools like PeakHour, iStat or LittleSnitch? Nope. Flushing cache? rebooting? Load/unload DNSResolver… ?

Absolutely nothing I could do would stop these mysterious messages.

Then this morning I found it.

I turned off “Back to my Mac” in iCloud preferences, and the messages, after weeks, finally stopped. (Yes, a few weeks ago, I turned in on for the first time… and then forgot about it.)

I could speculate, but frankly I’m too relieved to bother.

Just FYI.

Tracy
www.valleau.gallery

Leave a Reply

Your email address will not be published. Required fields are marked *