Murkworks web update

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 209.20.199.10 or 209.20.199.11, 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!

Published by

Angela Korra'ti

As Angela Highland, Angela is the writer of the Rebels of Adalonia epic fantasy series with Carina Press. As Angela Korra'ti, she writes the Free Court of Seattle urban fantasy series. She's also an amateur musician and devoted fan of Newfoundland and Quebecois traditional music.

4 thoughts on “Murkworks web update”

  1. The problem is between iinet and door. If I do a traceroute to 209.20.199.11, it traces through iinet to “gateway.murkworks.net” (209.20.178.33) and then times out. ping and telnet to port 80 are both unresponsive.

    At this point AFAICT only uplake.org is pointed at iinet, thanks to having 3rd party DNS. If their DNS can actually *get* updated, I’d say don’t worry about the kludge; they only have another day before their cache times out, and you’ll be good to go.

    1. I’m not sure what the problem is specifically–it’s tough to diagnose outside the Murk because Dara says she’s packet-blocking ping and traceroute anyway to newmoon and lodestone. So those aren’t going to be helpful.

      I don’t have quite enough net fu to know what else to check though.

Comments are closed.