Confirmed: this is not just me.
https://mastodon.social/@waldoj/113394127909972080
Here’s a hint as to what’s wrong with system-level networking services on macOS 15.1: Safari has inconsistent DNSSEC signature problems, while Chrome and Firefox (which use their own networking engines) do not. Every query has a different subset of signature problems.
I think I'm too rusty on cryptography implementation to meaningfully debug this further; here's hoping Apple patches this soon.
@waldoj I found a bug where my Yubikey doesnt work and boy was that a fun heart attack when trying to access my retirement accounts this morning. They really phoned it in on these releases.
@waldoj 30 seconds sounds like DNS timeout. Maybe do a “scutil --dns” and see if anything looks off?
I’ve just started my upgrade on my MacBook Air m3
@sfrazer434 I had the same theory last night, but I had no trouble running DNS lookups while Safari was unresponsive. That said, it could still be DNS (it’s almost always DNS!), but within Safari.
@waldoj interesting. I may not actually encounter the problem, then. I don’t use Safari all that regularly on mine.
Just in case, though, I’m keeping my work machine on 14.7 for a bit longer
@waldoj Running any network filters, security malware, VPN things, content blockers, etc?
Does the behavior replicate on a fresh user account?
@atlauren Oh, sure, I’m running all kinds of things like that, and now that I’ve learned others are also seeing this, I’ll start down that debugging path this evening.
@waldoj My impression is DNSSEC is widely considered a failure.
@feld Oooh, that’s a fine point. I will test that.