DNS propagation can sometimes take a while.

[code]c:\>nslookup mersenne.org 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: mersenne.org
Address: 66.181.10.42


c:\>nslookup mersenne.org 4.2.2.2
Server: b.resolvers.Level3.net
Address: 4.2.2.2

Non-authoritative answer:
Name: mersenne.org
Address: 66.181.10.42
[/code]

[QUOTE=TheMawn;380697]As of this moment the website is inaccessible for me. Not to sound impatient or anything, just letting you know in case this is unusual.[/QUOTE]

Yup. Like I said, we're waiting on some DNS changes right now but if you want to leap forward, you can add those entries to your HOSTS file.

I guess I could put something up on the old server... a place holder saying "if you're seeing this, you're seeing the old server", but that would just confuse anyone who doesn't read this thread and doesn't know what's happening. :smile:

[QUOTE=Madpoo;380699]Yup. Like I said, we're waiting on some DNS changes right now but if you want to leap forward, you can add those entries to your HOSTS file.

I guess I could put something up on the old server... a place holder saying "if you're seeing this, you're seeing the old server", but that would just confuse anyone who doesn't read this thread and doesn't know what's happening. :smile:[/QUOTE]

Got in :razz:

It's fast, but I don't know as there is probably no load on it...(?)

[QUOTE=kracker;380701]Got in :razz:

It's fast, but I don't know as there is probably no load on it...(?)[/QUOTE]

Yeah, it's fast. I *hope* it's just as fast when more people are using it.

FYI, George is doing some sanity checks on the migrated database to make sure we're not missing anything critical.

He may also take this time to do some much needed SQL tweaks with the indexes.

Once everything checks out, those DNS changes will happen.

Just on the off chance it's all fubar on the new setup, I'll hold myself personally responsible for taking any changes made on the new site by anyone using a HOSTS file entry to hit the new box and migrate those changes back to the old setup... if it comes to that of course.

Always have a roll-back plan.

Cool, cool. I'm in, too.

It certainly is very fast. Work distribution map or top producers list comes up instantly.

I notice the customize... button in the top producers (if you wanted to look at the top-x for all-time stats) is still fairly slow. Small potatoes.

I would lower the TTL on the DNS records to something like 300 seconds instead of 3600 for the next migration so people don't have stale entries for long. Though the current setting of an hour isn't really that bad.

I'm holding off on the DNS changes while you folks are playing around using the Hosts settings. Consider yourselves beta testers.

I've done a count on the factors and LL results tables on the old server an new server. The counts match. IMO, those are the 2 absolutely critical tables.

[QUOTE=Mark Rose;380711]I would lower the TTL on the DNS records to something like 300 seconds instead of 3600 for the next migration so people don't have stale entries for long. Though the current setting of an hour isn't really that bad.[/QUOTE]Even so not all resolvers will honour such short durations. It still can take up to 24 hours to complete an IP address transition. Depending upon your local DNS server selection you might get a new IP within moments or many hours.

[QUOTE=retina;380717]Even so not all resolvers will honour such short durations. It still can take up to 24 hours to complete an IP address transition. Depending upon your local DNS server selection you might get a new IP within moments or many hours.[/QUOTE]

Interesting tidbit... last week I was moving equipment around between datacenters so we were temporarily hosting some of our websites out of our LA servers.

We'd lowered our TTL's to 300 seconds during the moves and not too surprisingly, all of the live traffic seemed to move over pretty quick.

What did surprise me was one of the clients in particular that REFUSED to look up the new IP address, even days later.

The bad apple? Pinterest. People can pin our pages, and when they do Pinterest will hit the site to get title, default image, etc and it kept hitting the old IP address even after 4 days. Really weird.

Besides Pinterest everything else got the new one within no more than an hour.

In the past I've seen some really misbehaved proxy servers in particular. I forget the brand name, but it was horrible... it would cache DNS lookups forever, or until it restarted.

Weird!

Entered new IP addr in hosts, and I can connect and login.
If I click anything in the menu from "summary" to "results" the connection will just reset.

Rebooted and still resetting.

Btw. CSS is garbling somewhat, if i address [URL="http://www.mersenne.org"]www.mersenne.org[/URL] instead of mersenne.org.

We're tracking down a PHP warning message right now....