dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
17
share rss forum feed


TSI Gabe
Premium,VIP
join:2007-01-03
Chatham, ON
kudos:7
reply to nbinont

Re: Google DNS versus ours

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 )


mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..
·TekSavvy Cable

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 Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:26

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


AkFubar
Admittedly, A Teksavvy Fan

join:2005-02-28
Toronto CAN.

Posted in the direct forum... no can read it...


nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom
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 Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:26
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 Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:26
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

nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom
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 Gabe
Premium,VIP
join:2007-01-03
Chatham, ON
kudos:7
reply to TSI Marc

Are you saying this is still happening now?


nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom
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.

nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom
reply to TSI Gabe

said by TSI Gabe:

Are you saying this is still happening now?

Yep, for the past 8 months. Everyday


TSI Gabe
Premium,VIP
join:2007-01-03
Chatham, ON
kudos:7

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.



TSI Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:26
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


nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom
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.

nbinont

join:2011-03-13
kudos:2
Reviews:
·Start Communicat..
·TekSavvy Cable
·Bruce Telecom

said by nbinont:

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.

Well, it seems like whatever Gabe did over the last week has fixed it for me! I verified that it was still acting up a few days ago (and it was), but tonight it seems to be resolving correctly the first time.

I waited for the cached entry to expire in TSI's DNS server, then asked it to resolve the site again. Last week it would fail a few times before finally getting something for the cache, and then be good until the cache expired again.

Tonight, after the cache expired it worked the first time. Waited for the cache to expire again (30 min expiry in this case), and tried again. Success again!

I assume I must be on one of Gabe's new DNS servers - and they seem to be working well!

Guess I'll have to go update my review...

Bugblndr

join:2010-03-02
Burlington, ON

Good news, time to change things up on my setup a bit and see for myself.


mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..
·TekSavvy Cable
reply to nbinont

said by TSI Marc:

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

You do realize that only the originator (and TSI) can read threads in TSI Direct, right? Not the rest of us, so posting links to those threads doesn't help anyone here.


TSI Marc
Premium,VIP
join:2006-06-23
Chatham, ON
kudos:26

said by mlord:

said by TSI Marc:

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

You do realize that only the originator (and TSI) can read threads in TSI Direct, right? Not the rest of us, so posting links to those threads doesn't help anyone here.

yeah hehe AkFubar pointed that out to me too.. hehe I didn't realise at the time.. looks like nbinont's issue is solved now too. so it's all good
--
Marc - CEO/TekSavvy