Secondary isn't handling it either, not long enough for the standard
timeout, you can wait 1 or 2 seconds and hit enter in Safari or some
other browser and it'll work right away.
There's a least some indication that this may be a Safari issue even
though it looks like classic slow DNS symptoms. I've noticed this much
more lately as well. The first time I go to a site.... just about any
site... in Safari I get the server not found message very quickly.
Reload and it loads quickly as normal. DNS for everything else I'm
doing seems just fine. Here's a thread about it on Macfixit. No
conclusions, just lots of reports from others of the same thing.
