[lowbloodsugar]

So many sites being reported as down, but change your DNS to something else (e.g. Google 8.8.8.8 and 8.8.4.4) and, after flushing your DNS cache, the sites are available. I was unable to get to ups.com or newegg.com (why yes, I am expecting a new toy), but after switching DNS and flushing DNS cache, I was able to get to both.

Specifically, 1.1.1.1 provided bad addresses (as opposed to no addresses), and removing 1.1.1.1 fixed my problem. By then it had returned a bunch of bad addresses and I had to flush my DNS cache.

[aix1]

Could you give an example of what you mean by a "bad address" in this context?

[lowbloodsugar]

This is from the time of incident:

Server: 1.1.1.1 Address: 1.1.1.1#53

Non-authoritative answer: Name: newegg.com Address: 23.35.185.6

vs

Server: 8.8.8.8 Address: 8.8.8.8#53

Non-authoritative answer: Name: newegg.com Address: 104.80.92.252

104.80.92.252 is newegg.com

23.35.185.6 is a server that provides an error message.

So 1.1.1.1 lied. The proper response would be to reply "I don't recognize that domain". Instead it said, "yeah, I know that, its here..."

Newegg was not down, and when I got macos to forget what it had cached from 1.1.1.1 I was able to use newegg.com fine.