account activation in 49 minutes!

[Monty]

Thanks FQ, I don't know how you guys do what you do so quickly, but I sure appreciate the fast service.

Best of luck with the NINE upgrades in the morning.

Mont

[Deb]

Oh Monty! You shouldn't advertise such things. We only pull out the red [speedy] carpet for you :P

Deb
- Always have loved the kudos ;)

[Monty]

well, I just did a quick count, and that last one made 39 here.

I want to share something I learned that will save anyone hooking a domain up lots of pain and suffering. Get the DNS for your site pointing at FQ's name servers before turning in your order to FQ.

We turned in the DNS request to register.com yesterday, I checked their records today and found them pointing the DNS at FQ. This afternoon, I turn in the order to FQ and wham! That way, when FQ pulls the switch, that domain is hot from the word go, with no caching issues, propagation problems, ect...ect.., all done in under 24 hours.

and again, thanks FQ for the speedy service.

Mont

ps, how about those purty new yellow mailing labels I made ;)

[Jeff]

Get the DNS for your site pointing at FQ's name servers before turning in your order to FQ.

I think it's a better idea to get the account with FQ setup and all the site files uploaded and ready to go before the DNS switches over. I would rather have a caching issue with a few people using AOL than lots of other people seeing an error page because the DNS record is pointing at a temporary void...

[Monty]

Jeff, having done it both ways, I disagree. To each his own, but if you do turn in the FQ order prior to the DNS records being updated, I would go fishing for several days some place where there are no phones. :P

Site owners repeatadly checking to see if a domain is running has caused me no end to the grief that AOL's millions of caches cause, and get one that has an itty bitty ISP in the backwoods serving them, and you can all but forget it for days. I have never seen a case where the DNS records pointed to a non FQ server, and FQ's servers being able to be seen by my clients, or myself, via the www browser method.

What I have done is simply explain they will be down for 24 hours, and for me, that has eliminated all propagation issues, phone calls, and emails.

Mont

===why isn't it working yet?

===it is, but you can't see it!

[Deb]

ps, how about those purty new yellow mailing labels I made They get noticed for sure! Of all the urls I see in a day...your's stands out Monty :P

For those not in the "know" yet...Monty has some fairly LARGE bright YELLOW mailing labels for his postal items. They GET SEEN.

For those not yet sticking their URLs on their checks, envelopes, and mailing labels...ahem.... what's the problem????

Deb
- Excellent Idea For All

[Jeff]

Jeff, having done it both ways, I disagree. To each his own, but if you do turn in the FQ order prior to the DNS records being updated, I would go fishing for several days some place where there are no phones.

Most of the websites I do aren't very time sensitive, so it's usually fine if a few AOL folks are seeing the old site for a few days, but if a website went down for several hours and error messages were being shown and visitors lost, I would probably be in big trouble and the phone would be ringing.