I pinged dyndns.net with our (then-current) IP addy from the DHCP server at verizon. It's still serving the one from before that. How long does it take to get a new IP addy through the system?
I verified that I could ssh into fray from the work machines, using the correct IP addy. So, yay!
Oddly, I couldn't ssh directly from my laptop to fray using the outside-universe IP addy. Perhaps the fact that they're both using that addy confuses things or something. I don't really need to be able to do this, because I can ssh around the internal network using internal IP addys.
I installed DarwinPorts and then irssi on fray, and verified that it all works (albeit with some significant delays that might be due to the fact that the terminal windows were logged in from here to there and back multiple times).
Today, though, things timeout. Turns out our old friend the balky wireless router and/or DSL modem is at fault. From time to time it needs rebooting, and (of course) verizon's DSL gives me a different IP addy when that happens, so I was trying the wrong IP addy. Must fix this.
So I can see this thing working, if I can find out what IP addy the home machines have at a given time. If dyndns doesn't propagate fast enough, is there another solution? I could set up a cron job at home to e-mail me the addy or ssh in or something twice a day, I suppose...
Oh, and thanks to mns for letting me use his network all this time. What with the moving thing coming up, that's apparently shut down for a month or two.
Can you introspect out loud? --CRwM
Can you introspect out loud? --CRwM[ Parent ]
The official word on DNS is that it takes 24 to 72 hours to propagate through the entire Internet. Realistically, it usually happens in just a few hours. Part of that depends on the time of day. In the old days, quite a few servers only updated once or twice a day and everyone down stream from them wouldn't get updated until after they did. Nowadays, most of the important servers get updated multiple times per hour.
