DNS servers tend to have about a 24-hour latency on detecting sites where [noparse]www.sitename.com[/noparse] now references a new IP number.
By the way, as a general bit of information, it appears that quite often, when [noparse]http://www.sitename.com[/noparse] will not resolve, [noparse]http://sitename.com[/noparse] will. It’s worth trying if people are having trouble accessing a newly moved site.
Finally, many people’s experience has been that anything accessed through Google gets the “secure site” warning, since Google has set all its functions to invoke that.
I will say something though: Ed, your board can get kinds rickety at times. I’m not leaving or nothing, because I love the content, but come on. It goes down way more that it should.
My employer blocks a number of websites (for example, youtube), and at one point today, I saw the “blockpage” screen. It sent a chill up my spine to think I might never be able to visit here on my lunch hour or while waiting for a lengthy download. I’m totally relieved to know that it was just a transient glitch!