Re: Way OT: OpenDNS
2008/9/10 nate <debian-user@aphroland.org>:
> Dotan Cohen wrote:
>
>> Are there any known problems / gotchas with OpenDNS? I do know that
>> they redirect google queries through their own servers and return ads
>> in place of unregistered domains, but those 'features' can be turned
>> off. Anything else that I should be aware of?
>
> Of course I'm sure you know that DNS has nothing to do with
> ping response times or network throughput.
>
I know, but because of the latency I suspect that DNS lookup is at
least part of the problem. I put the slow response times in just show
how poor my ISP performs in general, which is felt in every aspect of
their service. Even a few hours downtime every month is common.
> Maybe it's time to get a new ISP. I have 1Mbps/1Mbps ADSL
> and it's about 38ms to google, I also have 16Mbps/2Mbps cable
> modem and it's about 34ms to google.
>
If I could test drive every ISP for a week or two and then decide I
would, we have three to choose from. However, in my country we pay for
the last mile from a different company than the ISP. That is, I have
an ISP providing 'net to the last mile provider, and the last mile
provider own the connection between myself and the ISP. It generally
overcomplicates things and makes a for a ton of problems, not to
mention blame for shifting when something is wrong.
> If you don't have any other ISP options then perhaps you should
> consider moving to a location where there are more options if
> internet performance is that important to you. Or perhaps other
> options such as T1 lines etc are available at higher prices.
>
There are other considerations keeping my in the house we just bought
two years ago.
> I find it funny that so many people out there seem to expect
> to be able to get 10Mbit+ speeds for $20/mo. Then they get
> upset when they find out the system is 100x oversubscribed
> and ends up being slow as hell. You get what you pay for.
> Co-workers at my company are all pissed off because one of
> the branch offices is off line because the $40/mo DSL line
> has been down for days and the provider doesn't have a
> ETA for recovery. You get what you pay for.
>
Actually, we pay almost double that for a 1.5 MB/sec line. At the
time, it was from the most expensive ISP but they were great and were
worth the cost. And they were not afraid of the L-word. However, they
were bought by The Big Scary Monopoly ISP and now the service sucks.
However, the prices have changed enough in the market that the price
is competitive. I would gladly pay more for a better ISP.
> At the same time the company spends about $35k/mo on
> roughly 800Mbit of internet bandwidth which comes out
> to around $43/Mbit(average across 4 ISPs). Which to me
> is dirt cheap, I'm used to buying bandwidth in lower
> volumes, and at least from Tier 1 ISPs it's easily $95/Mbit,
> and easily double that in Europe/Asia in many cases.
>
> I read an article recently estimating costs for Verizon FiOS
> to be roughly $4,000 per subscriber just to get them wired
> up. Doesn't even take into account ongoing bandwidth costs
> associated with those accounts.
>
There was a great discussion on /. recently about this. In fact, that
is what got me thinking about OpenDNS and solutions in general.
> If you suspect OpenDNS as a problem you can always setup your
> own name server(s) for caching requests. I've never used
> OpenDNS myself though some systems at my company use it(not
> for much longer). I've run my own name servers for about 12
> years now(my authoritative name servers are on my DSL, moving
> to co-location this weekend).
>
I will play with TinyDNS and see if it helps. I mostly visit the same
sites and rarely have to experiment with new sites.
Thanks.
--
Dotan Cohen
http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת
ä-ö-ü-ß-Ä-Ö-Ü
Reply to: