For those of you keeping track, DNS changes have as of this afternoon still not fully made it out into the wild. I’m seeing several of our domains at half-propped status, with both versions (with and without www) not agreeing on whether they’re pointing at the old addresses or the new ones.
I cannot currently tell if this is an Apache problem, because the old addresses are not answering connections at all–if I try to throw my web browser directly at 220.127.116.11 or 18.104.22.168, the connection times out and never actually makes it to the servers. So there’s nothing in the Apache logs for me to debug. Note that the exact same servers are happily accepting web connections sent to the new addresses, though.
So, if you have web content with us on the Murk and you still can’t get to it, have patience and keep checking. Your domain probably isn’t fully propped yet. If you want to doublecheck whether it has or not, and you don’t know how to do that, here’s how:
- Windows computers: Open a command prompt and type ‘nslookup’, then a space, then your domain. For example, ‘nslookup annathepiper.org’.
- Mac computers or Linux: Open a command prompt and do the same thing as with a Windows computer, only using the ‘host’ command instead of ‘nslookup’. For example, ‘host annathepiper.org’.
If you get back an address that starts with 209, that’s the old address. One that starts with 173 is the new one.
Questions, let me know! And thanks for your patience, Murknet peeps!