I just hit "quote" to reply to this message, and it took about 12 seconds, yikes. I'm sure you're right. Let's give it a while. Here's an FYI... UPDATE: It took about 25 seconds to post this message.

Time to look up xoutpost.com A record
Generated by www.DNSstuff.com at 20:00:25 GMT on 18 Jan 2006.
Searching for xoutpost.com A record at i.root-servers.net Got referral to K.GTLD-SERVERS.NET. [took 183 ms]
Searching for xoutpost.com A record at K.GTLD-SERVERS.NET. Got referral to ns1.cedgecons.com. [took 89 ms]
Searching for xoutpost.com A record at ns1.cedgecons.com. Timed out. Trying again.
Searching for xoutpost.com A record at ns1.cedgecons.com. Reports an answer.

Record is:


Domain Type Class TTL Answer xoutpost.com. A IN 14400 64.62.200.216 xoutpost.com. NS IN 86400 ns1.cedgecons.com. xoutpost.com. NS IN 86400 ns2.cedgecons.com. ns1.cedgecons.com. A IN 14400 64.62.200.216 ns2.cedgecons.com. A IN 14400 64.62.200.210

Looking up at ns1.cedgecons.com.... Timed out.
Looking up at ns2.cedgecons.com.... Timed out.


Average of all 2 nameservers: 1246ms (plus 1684ms overhead).

Score: F

Took off 15 points for a nameserver timeout at ns1.cedgecons.com (causes lengthy delays and extra packets).
Took off 15 points for a nameserver timeout at ns2.cedgecons.com (causes lengthy delays and extra packets).
Took off 25 points for >700ms average response time.

Note: The 1684ms overhead is the time it takes to get your NS records from the parent servers, and indicates a worst-case scenario (normally, the resolving DNS server would have the common parent server entries cached, and would know the parent server(s) that were responding most quickly). The best times since the last time this web server was last restarted are: 1ms average response, plus 6ms overhead. Note that these times are from a server located in the United States; if most of the people using your DNS are outside of the United States, your actual results may be better than what is shown here. A rating of 'B' or higher is generally good (this tool is very picky!). This tool is designed to make an educated guess about speed, and to point out potential factors that may reduce the DNS speed, and it is not perfect.