TekSavvy → Re: Google DNS versus ours

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.

Yep, for the past 8 months. Everyday

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.

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.

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.

Thanks! I'll follow up and try to reproduce it.

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...

Me too that's why I switched to using google a couple of years ago. I'll try out the TSI ones again.

There's no reason TSI couldn't anycast the DNS server IPs so that the same DNS IPs are used anywhere in TSI's territory :P Of course, that's kind of pointless since the vast majority of people use DHCP/PPPoE to automatically set the DNS servers anyhow. Most of the people setting theirs by hand are DNS ricers :P

well.. there is one good reason.. and well, it's that it would take a bit of lifting to do it and make sure it's done right and for what? not much value..

we'd have to move everything else off that class C...

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...

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

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