Murkworks web update

[annathepiper]

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!

Mirrored from annathepiper.org.

Comments

[wrog]

Could it be a routing problem?

If you stick a hub between your DSL modem and your outbound interface, plug a laptop into it configured with some IP that's plausibly on the same subnet as your DSL's gateway (...or if you want to be completely polite, you disconnect the phone line while you're doing your test and use your DSL gateway's IP address -- not that you care much about being polite to them at this point...), can that laptop talk to your apache server? It should. If it can't, then no one can.

Seems to me once one has more than one connection to the outside world, you either need two separate local nets and thus two physically separate interfaces on each of your (apache/whatever) server boxes or there's some fancy shit happening in the router that's hooked up to both gateways to deal with the two traffic streams being on the same network segment and keeping straight which is going where (and I particularly have no idea how NAT would even work in this world, if you're doing that).

Not that it isn't possible -- seems like somebody ought to have solved this problem by now -- but if it's not something one ordinarily does on a regular basis, I wouldn't expect to get it configured right the first time.

(e.g., I'm pretty sure said router can't just have a single default route pointed at the comcast gateway because if that's diverting the ACK replies to the SYNs that are coming in via the DSL gateway, then that completely hoses all TCP connections on the DSL side).