sfworks
Apr 21 2004, 05:56 PM
Hey guys. I'm having an issue I'm hoping you can help me out with.
Whenever I go to my website or any of my subdomains it's taking as long as 15- 20 seconds before it starts loading up the page. It's just sitting there with the "website contacted, waiting for reply message". Once it starts to load it's ok, it's just that initial respons that is going really slow (and no it's not all the time but it's been a lot more noticable lately).
I've connected to other web sites I've seen listed here in the forums and those all seem to connect fast.
My domain is
sfworks.comIs anyone else having this problem? I'm wondering if it's a DNS issue as the other sites I've looked at are on other name servers and the name server(s) I'm using are responding kind of slow
DNS Stuff Timing. at 38ms compared to an typical response of 12ms. It's not as bad as it was yesterday either. Yesterday I was getting well over 100ms(plus overhead) and my site was taking even longer to make the initial connection.
Thanks
Alexandre
Apr 21 2004, 06:59 PM
sfworks
Apr 21 2004, 07:12 PM
I just tried those link and got an A+ then an A for google, an A for Yahoo twice , and an F for sfworks.com 3 times before getting a C on the fourth try. It's looking like ns18 is the problem
Domain Type Class TTL Answer sfworks.com. A IN 14400 67.15.36.4 sfworks.com. NS IN 14400 ns19.hostony.net. sfworks.com. NS IN 14400 ns18.hostony.net. ns18.hostony.net. A IN 84450 67.15.24.116 ns19.hostony.net. A IN 14400 67.15.36.4
Looking up at ns18.hostony.net.... Timed out.
Looking up at ns19.hostony.net.... Reports 1 A record(s). 38ms.
Average of all 2 nameservers: 1524ms (plus 200ms overhead).
Score: F
Took off 15 points for a nameserver timeout at ns18.hostony.net (causes lengthy delays and extra packets).
Took off 2 points since ns18.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.
Alexandre
Apr 21 2004, 07:19 PM
I have fixed the problem with ns18.hostony.net.
Please try again.
Sorry for maybe inconvenience.
sfworks
Apr 21 2004, 08:27 PM
I don't think the problem is fixed I'm still getting fairly high response times. Generally they are in the 45-60ms range but many times they are way over 100ms and even over 1000ms.
I'm really not trying to nag. Since you guys got the new hardware in the service has been much more reliable and I've had very few issues. I'm only bringing this up because several clients have brought it to my attention. I've had people think my site is down because of the long connection times.
Generated by www.DNSstuff.com at 20:18:57 GMT on 21 Apr 2004.
Searching for A record for sfworks.com at h.root-servers.net: Got referral to G.GTLD-SERVERS.NET. [took 120 ms]
Searching for A record for sfworks.com at G.GTLD-SERVERS.NET.: Got referral to ns18.hostony.net. [took 103 ms]
Searching for A record for sfworks.com at ns18.hostony.net.: Reports an answer.
Record is:
Domain Type Class TTL Answer sfworks.com. A IN 11551 67.15.36.4 sfworks.com. NS IN 11551 ns19.hostony.net. sfworks.com. NS IN 11551 ns18.hostony.net.
Looking up at ns18.hostony.net.... Reports 1 A record(s). 160ms.
Looking up at ns19.hostony.net.... Reports 1 A record(s). 64ms.
Average of all 2 nameservers: 112ms (plus 223ms overhead).
Score: C
Took off 20 points since ns18.hostony.net does not respond authoritatively (can cause unexpected responses and add delays).
Took off 2 points since ns18.hostony.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 4 points for >80ms average response time.
Alexandre
Apr 21 2004, 09:36 PM
sfworks
Apr 21 2004, 11:53 PM
Alexandre,
Thanks for all you help on this. The site seems to be responding much quicker now. Of course I went to check my site when you guys were rebooting the server but now it looks like the server is back up and the response time is 100x better. No more hesitation and my pages of thumbnails loads noticably quicker.
The dns stuff test is giving you guys an A now.
Thanks!
Alexandre
Apr 22 2004, 12:21 AM
Don't mention it.
MartinB
Apr 22 2004, 02:39 AM
wizhosting.com.ar is getting a "F"
Looking up at ns8.hostony.net.... [Had to look up A record for ns8.hostony.net; assume +200ms]...Reports 1 A record(s). 350ms.
Looking up at ns2.hostony.com.... [Had to look up A record for ns2.hostony.com; assume +200ms]...Reports 1 A record(s). 474ms.
Average of all 2 nameservers: 412ms (plus 693ms overhead).
Stanly
Apr 22 2004, 02:51 AM
As I can see at
http://dnsstuff.com/tools/lookup.ch?name=w...g.com.ar&type=A it is 'cause of your national domain name registrar:
at first request is going to ns1.retina.ar, ATHEA.ar, etc.
Our name servers are working correctly - I've just checked again for you.
VVV
Apr 22 2004, 01:05 PM
I have the same problem with all my domains (www-sharp.com, oledbdirect.com, managed-vcl.com) located on the same server21 (67.15.36.4).
There is a big (5-30 seconds) delay before loading any web-page. This happens only for HTTP, FTP and shell works without any delays. Sometimes delay exists, sometimes - not. It seems that period 12:00 GMT - 18:00 GMT is affected. This continue some days.
Delay exists at the moment I write this. Currently delay is:
server1 - 6 sec.
server7 - 7.2 sec.
server8 - 2.4 sec.
server12 - 6.5 sec.
server17 - 20.5 sec.
server19 - 4.4 sec.
server21 - 18.8 sec.
other servers - < 2 sec.
sfworks
May 5 2004, 07:33 PM
Hey guys, I'm still having problems connecting to my site. I know you said on another posting about this problem you were looking into it. I just wanted to add a little more info.
I'm running a program that sends a small http request to a web host and logs the response times. This is not a ping. Pings to the server are fine. As you can see, connections to my domain are taking a long time especially compared to hostony's main page. I understand that the main site needs to be up especially when other servers are having problems but I'm just using it for a comparison. I also had it log 67.15.16.19 (which I think is server 20) to show that other servers aren't nearly as bad.
Here are my results from today (I've used it other days with very similar results). These are just some samples out of the log. Times are in seconds so 00:00:35.250 would be 35.250 seconds.
I love your customer service and your hosting packages are great but his has been going on for quite a while now and it's making accessing my site intolerable slow. Is there anything that can be done?
sfworks.com
5/5/2004 10:25:56 AM - AUTO-POLLING STARTED.
5/5/2004 10:26:04 AM - SUCCESS sfworks.com 00:00:07.375.
5/5/2004 10:27:02 AM - SUCCESS sfworks.com 00:00:05.359.
5/5/2004 10:28:03 AM - SUCCESS sfworks.com 00:00:06.375.
5/5/2004 10:29:13 AM - SUCCESS sfworks.com 00:00:16.391.
5/5/2004 10:30:20 AM - SUCCESS sfworks.com 00:00:23.391.
5/5/2004 10:31:16 AM - SUCCESS sfworks.com 00:00:19.969.
5/5/2004 10:32:17 AM - CONNECTION FAILED.
5/5/2004 10:32:17 AM - Connection Failed.
5/5/2004 10:33:13 AM - SUCCESS sfworks.com 00:00:16.828.
5/5/2004 10:34:11 AM - SUCCESS sfworks.com 00:00:14.453.
5/5/2004 10:35:19 AM - SUCCESS sfworks.com 00:00:22.656.
5/5/2004 10:36:22 AM - SUCCESS sfworks.com 00:00:25.719.
5/5/2004 10:37:12 AM - SUCCESS sfworks.com 00:00:15.797.
5/5/2004 10:38:18 AM - SUCCESS sfworks.com 00:00:21.687.
5/5/2004 10:39:11 AM - SUCCESS sfworks.com 00:00:14.703.
5/5/2004 10:40:10 AM - SUCCESS sfworks.com 00:00:13.359.
5/5/2004 10:41:03 AM - SUCCESS sfworks.com 00:00:07.062.
5/5/2004 10:42:04 AM - SUCCESS sfworks.com 00:00:08.016.
5/5/2004 10:43:32 AM - SUCCESS sfworks.com 00:00:35.250.
5/5/2004 10:44:07 AM - SUCCESS sfworks.com 00:00:10.187.
5/5/2004 10:45:02 AM - SUCCESS sfworks.com 00:00:06.078.
5/5/2004 10:46:04 AM - SUCCESS sfworks.com 00:00:07.437.
5/5/2004 10:47:17 AM - CONNECTION FAILED.
5/5/2004 10:47:17 AM - Connection Failed.
5/5/2004 10:48:08 AM - SUCCESS sfworks.com 00:00:11.875.
5/5/2004 10:49:15 AM - SUCCESS sfworks.com 00:00:18.734.
5/5/2004 10:50:12 AM - SUCCESS sfworks.com 00:00:15.719.
5/5/2004 10:51:11 AM - SUCCESS sfworks.com 00:00:14.609.
5/5/2004 10:52:11 AM - SUCCESS sfworks.com 00:00:14.734.
5/5/2004 10:53:10 AM - SUCCESS sfworks.com 00:00:13.766.
5/5/2004 10:54:10 AM - SUCCESS sfworks.com 00:00:13.266.
5/5/2004 10:55:09 AM - SUCCESS sfworks.com 00:00:12.234.
5/5/2004 10:56:07 AM - SUCCESS sfworks.com 00:00:11.047.
5/5/2004 10:57:11 AM - SUCCESS sfworks.com 00:00:14.266.
5/5/2004 10:58:07 AM - SUCCESS sfworks.com 00:00:10.437.
5/5/2004 10:59:11 AM - SUCCESS sfworks.com 00:00:14.172.
5/5/2004 11:00:10 AM - SUCCESS sfworks.com 00:00:13.156.
5/5/2004 11:01:06 AM - SUCCESS sfworks.com 00:00:10.125.
/5/2004 10:26:07 AM - AUTO-POLLING STARTED.
5/5/2004 10:26:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:27:08 AM - SUCCESS hostony.com 00:00:00.375.
5/5/2004 10:28:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:29:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:30:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:31:08 AM - SUCCESS hostony.com 00:00:00.328.
5/5/2004 10:32:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:33:08 AM - SUCCESS hostony.com 00:00:00.359.
5/5/2004 10:34:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:35:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:36:08 AM - SUCCESS hostony.com 00:00:00.328.
5/5/2004 10:37:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:38:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:39:08 AM - SUCCESS hostony.com 00:00:00.359.
5/5/2004 10:40:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:41:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:42:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:43:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:44:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:45:08 AM - SUCCESS hostony.com 00:00:00.359.
5/5/2004 10:46:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:47:08 AM - SUCCESS hostony.com 00:00:00.343.
5/5/2004 10:44:15 AM - AUTO-POLLING STARTED.
5/5/2004 10:44:15 AM - SUCCESS 67.15.16.19 00:00:00.172.
5/5/2004 10:45:15 AM - SUCCESS 67.15.16.19 00:00:00.203.
5/5/2004 10:46:16 AM - SUCCESS 67.15.16.19 00:00:00.265.
5/5/2004 10:47:22 AM - SUCCESS 67.15.16.19 00:00:06.547.
5/5/2004 10:48:15 AM - SUCCESS 67.15.16.19 00:00:00.172.
5/5/2004 10:49:15 AM - SUCCESS 67.15.16.19 00:00:00.187.
5/5/2004 10:50:15 AM - SUCCESS 67.15.16.19 00:00:00.156.
5/5/2004 10:51:16 AM - SUCCESS 67.15.16.19 00:00:00.484.
5/5/2004 10:52:15 AM - SUCCESS 67.15.16.19 00:00:00.187.
5/5/2004 10:53:15 AM - SUCCESS 67.15.16.19 00:00:00.187.
5/5/2004 10:54:15 AM - SUCCESS 67.15.16.19 00:00:00.187.
5/5/2004 10:55:15 AM - SUCCESS 67.15.16.19 00:00:00.187.
5/5/2004 10:56:16 AM - SUCCESS 67.15.16.19 00:00:00.234.
5/5/2004 10:57:15 AM - SUCCESS 67.15.16.19 00:00:00.156.
5/5/2004 10:58:15 AM - SUCCESS 67.15.16.19 00:00:00.172.
5/5/2004 12:05:13 PM - SUCCESS 67.15.36.4 00:00:11.657.
5/5/2004 12:06:14 PM - SUCCESS 67.15.36.4 00:00:12.000.
5/5/2004 12:07:09 PM - SUCCESS 67.15.36.4 00:00:07.110.
5/5/2004 12:08:15 PM - SUCCESS 67.15.36.4 00:00:13.485.
5/5/2004 12:09:16 PM - SUCCESS 67.15.36.4 00:00:14.516.
5/5/2004 12:10:16 PM - SUCCESS 67.15.36.4 00:00:14.703.
5/5/2004 12:11:12 PM - SUCCESS 67.15.36.4 00:00:10.032.
5/5/2004 12:12:19 PM - SUCCESS 67.15.36.4 00:00:17.047.
5/5/2004 12:13:12 PM - SUCCESS 67.15.36.4 00:00:10.141.
5/5/2004 12:14:12 PM - SUCCESS 67.15.36.4 00:00:10.063.
5/5/2004 12:15:16 PM - SUCCESS 67.15.36.4 00:00:14.063.
5/5/2004 12:16:15 PM - SUCCESS 67.15.36.4 00:00:13.172.
5/5/2004 12:17:07 PM - SUCCESS 67.15.36.4 00:00:05.328.
5/5/2004 12:18:06 PM - SUCCESS 67.15.36.4 00:00:04.110.
5/5/2004 12:19:11 PM - SUCCESS 67.15.36.4 00:00:08.907.
5/5/2004 12:20:14 PM - SUCCESS 67.15.36.4 00:00:12.219.
5/5/2004 12:21:23 PM - CONNECTION FAILED.
5/5/2004 12:21:23 PM - Connection Failed.
5/5/2004 12:22:18 PM - SUCCESS 67.15.36.4 00:00:15.891.
Alexandre
May 5 2004, 08:34 PM
Daer sfworks
The Domain Name System (DNS) is a distributed Internet directory service. DNS is used mostly to translate between domain names and IP addresses, and to control Internet email delivery. Most Internet services rely on DNS to work, and if DNS fails, web sites cannot be located and email delivery stalls.
This service always running on the server, but sometimes it needs to be restarted.
Your monitiring software gives failure when BIND (DNS) is being restarted.
As I see all is ok:
http://www.dnsstuff.com/tools/dnstime.ch?n...orks.com&type=A
sfworks
May 5 2004, 08:58 PM
Alexandre,
My problem is, it's taking 35 seconds to connect to my website sometimes and 1 second other times. Usually it's longer than shorter.
I'm not talking about dowload times, ping times or dns response times. I'm talking about establishing an http connection. It should take less than a second, not 10 seconds, not 20 seconds and really not 35 seconds as it does sometimes.
It's not my ISP or local network traffic. I'm currently sitting on a t1 with a fiber backbone. I've also tried this from other locations and other ISPs. It's only my website (or other sites on 67.15.36.4). I don't have this delay any place else.
michaeljacob
May 6 2004, 01:29 AM
i'm having similar troubles with my account.... sometimes the site just pops up after i click go, and other times (more often that not) it takes forever just to connect. its not just me, because visitors to my site from both coasts have said the same thing... when i test it on dnsreports.com i get a C+ at best.
http://www.dnsstuff.com/tools/dnstime.ch?n...rica.com&type=Ait seems like ns18.hostony.net is the bad seed.
thanks for the help,
mike.
jchrastina
May 6 2004, 01:33 AM
I have never been to sfworks.com before .... not in my cache .... I just tried sfworks.com at home on ADSL (1.5 Mbps down) and your site popped up INSTANTLY. Digital photography ... weddings, etc. No speed proble at all bouncing from page to page.
ping times to 67.15.36.4 are around 60ms.
sfworks
May 6 2004, 02:18 AM
jchrastina,
Thanks for checking my site for me. Right now it's loading really fast for me too (about 7pm pacific time). It's usually fine in the evening and early morning. Right in the middle of the though is when it's at its slowest. The odd thing is, once I've made my initial browser connection to sfworks.com (at the times it's going slow) I can click on all of my sub pages and they're fine. It's just that initial connection that seems to be the problem.
michaeljacob
May 6 2004, 02:45 AM
QUOTE(sfworks @ May 6 2004, 02:18 AM)
jchrastina,
Thanks for checking my site for me. Right now it's loading really fast for me too (about 7pm pacific time). It's usually fine in the evening and early morning. Right in the middle of the though is when it's at its slowest. The odd thing is, once I've made my initial browser connection to sfworks.com (at the times it's going slow) I can click on all of my sub pages and they're fine. It's just that initial connection that seems to be the problem.
bingo! the initial takes forever, the other sub pages just fly... at first i thought it was server load, but even my cPanel access runs really fast, and the system status shows virtually no load. so its something external of the actual webserver.
mike
relayamerica.com
sfworks
May 6 2004, 03:43 PM
Here's a few of the logs I've generated so far. All times are Pacific Time.
This one is from the late morning and afternoon of May 5th. It shows ridiculously high http response times.
sfworks_2004-05-05.txtThis one is from the evening of May 5th through the early morning of May 6th. You can see the response times are perfectly normal at night and very rarely take over 1 second until about 5:30AM PST when the number of requests over 1 second starts to increase. By 7:30 AM PST many of the response are taking over 10 seconds.
sfworks_2004-05-06.txtFor a comparison here's the hostony http log. As you can see the main server is never over half a second in it's response.
hostony_2004-05-06.txtRight at the moment everything is loading nice and smooth, very fast. I'll let you all know if it starts slowing down again.
ghanem
May 7 2004, 03:31 AM
hi,
why my site is gett B- and C
The link to DNS Timecan you please check or let me know the reasons..
Regards.
Alec
May 7 2004, 04:56 AM
We've fixed dns issue with your domain.
Check it now
MartinB
May 7 2004, 11:44 AM
The link to dns timesmy site is getting and F like the best letter. i think this is not only for ".ar" TLD (only 8 points for that)
What do you think ? some thing to fix ?
thanks in advance.
MartinB
May 7 2004, 11:54 AM
Look, playing with dnsstuff, i discover the follow:
First at all, Im a reseller, and i have 2 private label nameservers:
- ns1.wizhosting.com.ar
- ns2.wizhosting.com.ar
Now, when i do the DNS Time for some domain from my clients, i always get:
Took off 20 points since ns2.wizhosting.com.ar does not respond authoritatively (can cause unexpected responses and add delays).for all my clients domains.
ej: altatechnos.com, carranza-asociados.com, cedene.com.ar, mujicalainez.org.ar, f28.net, etc etc
Sounds like problems with ns2.wizhosting.com.ar
thanks and sorry for spend your time.
-Martin
ghanem
May 7 2004, 05:32 PM
Hi,
Thank you for your fast response..
yes its ok now with www.bahchat.com
I have other domains with you givin the same results B- & C+ or less even..
Site List:
www.bah4u.com
www.bahchat.net
www.bahcars.net
Regards.
Alexandre
May 7 2004, 09:03 PM
Fixed.
MartinB
May 9 2004, 01:18 PM
I still getting F from all my domains:
ALTATECHNOS.COM
CARRANZA-ASOCIADOS.COM
DANIELDEHOOP.COM.AR
DISCOVERINGBOLIVIA.COM
ELMENSAJEROAG.COM.AR
F28.NET
LOSBLENDINGER.COM.AR
NANDEROGABAR.COM.AR
SIEK.COM.AR
artescenico.com.ar
cedene.com.ar
ervisis.com
monitoraseguridad.com.ar
mujicalainez.org.ar
tostadense.com.ar
trial1.com.ar
example:dns time for siek.com.arCODE
Score: F
Took off 8 points for ".ar" TLD (extra lookups likely will be necessary to find the parent servers).
Took off 8 points for having no glue at a parent server [adds 2 extra packets to lookup].
Took off 6 points for having no glue for ns2.wizhosting.com.ar [adds 2 extra packets to lookup].
Took off 6 points for having no glue for ns1.wizhosting.com.ar [adds 2 extra packets to lookup].
Took off 20 points for >200ms average response time.
thanks, i hope you can do something for fix it.
Vanya
May 9 2004, 02:06 PM
Looks like your TLD problem (.ar)
There is no additional section with name servers address in your dns zone files. That's why NS addresses must be located separately.
MartinB
May 9 2004, 03:20 PM
QUOTE
There is no additional section with name servers address in your dns zone files. That's why NS addresses must be located separately.
??
sorry, i don't understand
Vanya
May 9 2004, 04:10 PM
In other words the problem is with your registrar.
MartinB
May 9 2004, 06:41 PM
ah, ok!
what can/need i do for solucionate this problem ? (is this a problem, right?)
Alec
May 9 2004, 09:51 PM
Your domain is not TLD domain (internation domain name) and set up in international name servers. So dns lookup take much of time to detect your domain.
MartinB
May 10 2004, 01:12 PM
its clear.
so, now i need to do a balance of what more domains i have (if .com or .com.ar) and if i have > % of NO TLDs i need buy a .com domain for my nameservers...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.