The whois server responsible for nchomeschool.org is no...

[hotwater]

Register.com reports "The whois server responsible for nchomeschool.org is not responding."[nbsp][nbsp]I seem to have registered correctly, and register.com indicates that this is now a 'taken' domain, and FutureQUest says nchomeschool.org is now on a Future Quest, so why do I get the error message, and why can't I see www.nchomeschool.org (http://www.nchomeschool.org) pages?

I just signed up yesterday, so do I just need to be patient?[nbsp][nbsp]How long should it take?

[Terra]

1) I've seen several whois servers offline throughout this weekend, whois.opensrs.org being one of them...

2) ('nchomeshool.org' is now on a FutureQuest), means that your account has been setup and activated on the FutureQuest servers to where you can login via your temporary information (IP) and start building...[nbsp][nbsp]However, visitors being able to see your domain rely on #3.

3) After registering your domain name, it must be entered into the 'Root Name Servers'...[nbsp][nbsp]When a browser goes to visit your domain, the following flow happens:
browser (acme.com) --> ISP DNS
if ISP has the answer, sent back IP
if ISP does *not* have the answer; then
[nbsp][nbsp]ISP --> Root Name Server (ask for acme.com)
[nbsp][nbsp]Root Name Server replies, you need to ask ns1.yourhost.com
[nbsp][nbsp]ISP --> ns1.yourhost.com (ask for acme.com)
[nbsp][nbsp]Host name server (authoritative) --> ISP (acme.com has this IP)
[nbsp][nbsp]ISP --> browser (you can find acme.com here)
fi

You cannot see your domain because you do not yet have an entry in the 'Root Name Servers' stating that we are Authoritative for your domain...

Please allow up to 48 hours for your domain to be entered into these critical Root Name Servers...[nbsp][nbsp]If that time passes by and still no results, then you can run the following on our servers to double-check:

$dig @a.root-servers.net nchomeschool.org

If you get a response like:
ORG.[nbsp][nbsp] 1D IN SOA[nbsp][nbsp]A.ROOT-SERVERS.NET. hostmaster.nsiregistry.NET. (

then it's not there yet...

The only remedy to this particular problem is to contact the Registrar and have them fix the problem...[nbsp][nbsp]Most likely it's gotten stuck in a queue somewhere, or just totally dropped on the floor...

As with all technology, things do go wrong - you just need to be vigilant and ensure that you contact the responsible parties to address the problem...

--
Terra
--This should be a FAQ, perhaps a nice process flow diagram - but then again I swear I only read the articles--
FutureQuest