Help - Search - Members - Calendar
Full Version: More slow responses
Hostony Board > General Support > General Support
tresuvesdobles
I have a Windows account and responses from my DNS are also very slow during th last days. What is happening to the connections at Hostony end?

Response time sample taken from dnsstuff.com

QUOTE
Time to look up tresuvesdobles.com A record
Generated by www.DNSstuff.com at 21:29:39 GMT on 11 May 2004.
Searching for A record for tresuvesdobles.com at b.root-servers.net:  Got referral to A.GTLD-SERVERS.NET. [took 98 ms]Searching for A record for tresuvesdobles.com at A.GTLD-SERVERS.NET.:  Got referral to win2.hostony.net. [took 49 ms]
Searching for A record for tresuvesdobles.com at win2.hostony.net.:  Timed out.  Trying again.
Searching for A record for tresuvesdobles.com at win1.hostony.net.:  Reports an answer.

Record is:


Domain Type Class TTL Answer tresuvesdobles.com. A IN 14400 69.56.161.186

Looking up at win1.hostony.net.... Reports 1 A record(s). 28ms.
Looking up at win2.hostony.net.... Timed out.


Average of all 2 nameservers: 1521ms (plus 5210ms overhead).

Score: F

Took off 2 points since win1.hostony.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 15 points for a nameserver timeout at win2.hostony.net (causes lengthy delays and extra packets).
Took off 2 points since win2.hostony.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 25 points for >700ms average response time.

Note: The 5210ms 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: 12ms average response, plus 92ms 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 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.
Stanly
We're checking this right now.
I'll keep you updated.
tresuvesdobles
Any news on this?

Answer times are much better now but I am afraid the slow times will come back as it has been happening in the last days.

Thanks in advance
Alexandre
Answer times will be much better after 72 hours.
To solve this problem we have made some changes in the DNS of our server.
All must be much better. after 72 hours.
tresuvesdobles
Ok, many thanks!

I have my hopes pinned on the changes you refer. rolleyes.gif

By now results are really poor again...

QUOTE
Time to look up tresuvesdobles.com A record
Generated by www.DNSstuff.com at 16:04:25 GMT on 12 May 2004.
Searching for A record for tresuvesdobles.com at g.root-servers.net:  Got referral to G.GTLD-SERVERS.NET. [took 204 ms]Searching for A record for tresuvesdobles.com at G.GTLD-SERVERS.NET.:  Got referral to win2.hostony.net. [took 114 ms]
Searching for A record for tresuvesdobles.com at win2.hostony.net.:  Timed out.  Trying again.
Searching for A record for tresuvesdobles.com at win1.hostony.net.:  Reports an answer.

Record is:


Domain Type Class TTL Answer tresuvesdobles.com. A IN 14400 69.56.161.186

Looking up at win1.hostony.net.... Reports 1 A record(s). 31ms.
Looking up at win2.hostony.net.... Timed out.


Average of all 2 nameservers: 1529ms (plus 5340ms overhead).

Score: F

Took off 2 points since win1.hostony.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 15 points for a nameserver timeout at win2.hostony.net (causes lengthy delays and extra packets).
Took off 2 points since win2.hostony.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 25 points for >700ms average response time.

Note: The 5340ms 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: 14ms average response, plus 89ms 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 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.


Regards
Vanya
It should be ok in a few hours.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2024 Invision Power Services, Inc.
IPS Driver Error

IPS Driver Error

There appears to be an error with the database.
You can try to refresh the page by clicking here