| reply to TSI Gabe
Re: Google DNS versus ours I have rarely agreed about google/openDNS being better than TSI's DNS servers. Namebench consistently showed TSI being faster, with no time-outs, etc for me. Bell's were consistently the worst (very slow, lots of time-outs, etc.).
If this means performance gets even better, I'm happy! |
|
 TSI GabePremium,VIP
join:2007-01-03
Chatham, ON
kudos:2 | reply to nbinont
The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working.
The second one...it's hard to tell, it's just a review that hasn't really been looked at to begin with.
The third one, the guy had just updated his DNS records on his own server, we forced a refresh for him as a courtesy.
--
TSI Gabe - TekSavvy Solutions Inc.
Authorized TSI employee ( »TekSavvy FAQ »Official support in the forum )
|
|
|
|
 nitzguyPremium
join:2002-07-11
Sudbury, ON
 ·TekSavvy DSL
| reply to TSI Gabe
said by TSI Gabe:No that's just one of the DNS Servers that's behind the cluster of DNS servers...please stop testing against it because it was just for testing...
I never tested against it to begin with  .
Was just curious....when I worked for a previous cable company, they had 4 DNS servers to autheticate, and it was always the 4th one that had the best results...presumably because it had the lowest load...so I set it as the primary manually....
Just was wondering if this was the case here... does .22 get more usage than .170 Gabe? |
|
| reply to TSI Gabe
Nice results on the DNS servers.
Where are they located? Are they in different sites etc for redundancy? |
|
mlord
join:2006-11-05
Nepean, ON
kudos:9 Reviews:
·Start Communicat..
 ·TekSavvy Cable
·TekSavvy DSL
| reply to TSI Gabe
said by TSI Gabe:The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working. That's probably his router, which probably IS using TSI's server. Very standard setup, that. |
|
 TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:14 | said by mlord:said by TSI Gabe:The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working. That's probably his router, which probably IS using TSI's server. Very standard setup, that. Gabe appears to have looked that one up at the time and wrote this later in the thread:
»Re: [Cable] Slow DNS resolution for site on Teksavvy
--
Marc - CEO/TekSavvy |
|
 AkFubarAdmittedly, A Teksavvy Fan
join:2005-02-28
Toronto CAN. | Posted in the direct forum... no can read it...  |
|
Reviews:
·TekSavvy Cable
·Bruce Telecom
·Start Communicat..
 ·voip.ms
| reply to mlord
said by mlord:said by TSI Gabe:The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working. That's probably his router, which probably IS using TSI's server. Very standard setup, that. Yep - my router using TSI's DNS servers. Though asking TSI's DNS servers directly with dig shows the same problem. |
|
TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:14 | reply to AkFubar
oh. hahaha, that's funny. I see says the blind man!?
looks like the first and the last are actually one and the same.
if we had problems with the dns servers.. we'd have thousands of calls... just look at the rogers outtage recently.. that's what happened.
--
Marc - CEO/TekSavvy |
|
TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:14 | reply to nbinont
said by nbinont:said by mlord:said by TSI Gabe:The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working. That's probably his router, which probably IS using TSI's server. Very standard setup, that. Yep - my router using TSI's DNS servers. Though asking TSI's DNS servers directly with dig shows the same problem. lets take a closer look see if we can figure out what's going on.
--
Marc - CEO/TekSavvy |
|
Reviews:
·TekSavvy Cable
·Bruce Telecom
·Start Communicat..
·voip.ms
| reply to AkFubar
said by AkFubar:Posted in the direct forum... no can read it...
Sorry everyone - the problem occurs when the specific address is NOT in the TSI DNS cache. If I posted the site everyone here would check it out and TSI would not be able to see the effect on the first request. Hence the Direct forum post. |
|
TSI GabePremium,VIP
join:2007-01-03
Chatham, ON
kudos:2 | reply to TSI Marc
Are you saying this is still happening now? |
|
Reviews:
·TekSavvy Cable
·Bruce Telecom
·Start Communicat..
·voip.ms
| reply to TSI Marc
said by TSI Marc:said by mlord:said by TSI Gabe:The first one, he's using 192.168.1.1 as his DNS server, not ours, hence why it's not working. That's probably his router, which probably IS using TSI's server. Very standard setup, that. Gabe appears to have looked that one up at the time and wrote this later in the thread: » Re: [Cable] Slow DNS resolution for site on Teksavvy Yes, but the first time I believe the dig command was was not going to the right server: »Re: [Cable] Slow DNS resolution for site on Teksavvy
And this problem happens regularly. but only on TSI. Very repeatable. |
|
Reviews:
·TekSavvy Cable
·Bruce Telecom
·Start Communicat..
·voip.ms
| reply to TSI Gabe
said by TSI Gabe:Are you saying this is still happening now?
Yep, for the past 8 months. Everyday |
|
TSI GabePremium,VIP
join:2007-01-03
Chatham, ON
kudos:2 | K...honestly this is going to be hard to reproduce now that we are running other DNS servers...I guess keep me posted if it happens again and I'll take another look. Since right now I'm able to resolve those domains just fine. |
|
jstory
join:2011-02-05
New Westminster, BC | reply to TSI Gabe
Just did.
Got a query response time of 76 msec and 75 msec, respectively, compared to 33 msec for 8.8.8.8.
mtr reports a ping of 13 msec, so maybe the server is just under heavy load. |
|
TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:14 | reply to nbinont
k, I've asked Gabe to look into it more closely. I'm sure it's something logical we just need to find what it is.
--
Marc - CEO/TekSavvy |
|
Reviews:
·TekSavvy Cable
·Bruce Telecom
·Start Communicat..
·voip.ms
| reply to TSI Gabe
said by TSI Gabe:K...honestly this is going to be hard to reproduce now that we are running other DNS servers...I guess keep me posted if it happens again and I'll take another look. Since right now I'm able to resolve those domains just fine.
Thanks! I'll follow up and try to reproduce it. |
|
TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:14 | reply to jstory
said by jstory:Just did.
Got a query response time of 76 msec and 75 msec, respectively, compared to 33 msec for 8.8.8.8.
mtr reports a ping of 13 msec, so maybe the server is just under heavy load.
Gabe responded to you earlier. you have to use the Vancouver DNS servers since you're in BC..
That's because Vancouver has separate DNS servers.
You need to use 76.10.191.198 & 199 (these servers are not yet updated though)
we too can make our IPs respond no matter where you are but we just haven't done that.. there's no real need.
Google has that 8.8.8.8 block anycasted.. it's a routing trick.. that make all the routers think that IP is really close but in fact there are srvers everywhere with the same IP...
--
Marc - CEO/TekSavvy |
|
 Mike2009
join:2009-01-13
Ottawa, ON
kudos:3
·TekSavvy DSL
| reply to HiVolt
said by HiVolt:Same thing I've experienced... Me too that's why I switched to using google a couple of years ago. I'll try out the TSI ones again. |
|
