Site move

[chase]

Sometime this month, maybe this weekend or next week, I'll be moving the site to a new server. Downtime should only be long enough to dump the database and move it. DNS TTL is already down to 1 hour but I'll post the new ip addresses here in advance of the move.

[01000101]

what's the reason?
If it's just a system hardware upgrade, could you list a spec comparison?

[chase]

Main reason: Company I colo with is moving out of the data center in Houston because the ownership changed and they are quadrupling the bandwidth charges. The server will now be in Dallas.

Switching from a colo plan with my own server to a managed private server (basically renting a server now). Going to add $15 dollars a month to my fees but I don't have to buy hardware.

Current server is dual 1133MHz PIII with 2 x 18GB SCSI disks (spanned to increase storage)

New server is dual 2000MHz AMD Opteron 246 with 2 x 80GB SATA disks (software mirrored)

The network backbones should be better in the Dallas data center so network speed should increase.

[Troy Martin]

Ye gods, I'm all for the downtime then!

[chase]

The new ip will be 174.136.63.246. Just wanted to let you guys know ahead of time in case any of you have an ISP that caches DNS entries longer than they should (many ISPs do). Move is probably still a couple days out.

[Troy Martin]

Hey, at least we now know you are running Apache

[VolTeK]

good luck with the switch, all of us will love the speed of the new server

[gravaera]

Np. I already receive so much from this site. It's no problem if you need to do what you've got to do. I'm just grateful for the resources.

[chase]

Should be today or tonight sometime so if you haven't copied down the new ip, 174.136.63.246, to put in your hosts file, now would be a good time.

[chase]

Moved. Let me know if anything seems broken on the forums or wiki. Still have a couple of things to do like configure the offline archiving of the wiki and some backup jobs but the site should be functioning for you guys.

[Troy Martin]

Shiny. And fast!

[Brynet-Inc]

It appears very responsive.. bonus, it's only 12 hops away.. and 10 of those hops appear within my ISP's wider network!

Let us know when you update the DNS records, your own name servers still use the old address.

[chase]

It appears very responsive.. bonus, it's only 12 hops away.. and 10 of those hops appear within my ISP's wider network!

Let us know when you update the DNS records, your own name servers still use the old address.

My DNS servers were updated hours ago before the site came online at the new ip. You are seeing something cached at your ISP or home if you are still getting the old values. You can compare:
dig @ns09.domaincontrol.com forum.osdev.org
With:
dig forum.osdev.org

[Brynet-Inc]

I did query your nameservers when I made that post, they are updated now.. but they weren't then.

EDIT: Actually, dig @ns{09,10}.domaincontrol.com osdev.org still returns 64.202.189.170.

[chase]

I did query your nameservers when I made that post, they are updated now.. but they weren't then.

EDIT: Actually, dig @ns{09,10}.domaincontrol.com osdev.org still returns 64.202.189.170.

That ip is fine and will not be changing (it is part of a redirect service that godaddy has). Only www.osdev.org, forum.osdev.org, f.osdev.org, wiki.osdev.org, and w.osdev.org changed.