Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Speed internet browsing via a local domain name server' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Speed internet browsing via a local domain name server
Authored by: cynikal on May 04, '05 12:02:15PM

"... We are having to make every single request to an external DNS server, thus creating a lag in initial response."

This is simply not true, we do NOT have to make 'every single request'. It only looks it up once, the first look up if it's not in our cache.. then the system caches that for a certain amount of time (determined by the authoritative dns server's TTL) using the lookupd daemon (read the man pages if you want more information). All requests to the website by name will use the lookup instead of making requests every single time.

Furthermore, this type of hint is irresponsible in that it causes extra, unnecessary load on the auhoritative name servers on the internet because that's the point of caching nameservers upstream, instead of every single computer running its own name service cache.

Also this behaviour of having to look up an address initially is no different than any other operating system, so i'm not sure where do you get off calling windows vs mac web browsing dog slow? Like the other post mentioned, this is pretty subjective. Maybe it's time to upgrade your mac? Try using a slow windows machine and the tables will be turned.



[ Reply to This | # ]
Irresponsible? I don't think so...
Authored by: j-beda on May 04, '05 12:16:00PM
Furthermore, this type of hint is irresponsible in that it causes extra, unnecessary load on the auhoritative name servers on the internet because that's the point of caching nameservers upstream, instead of every single computer running its own name service cache.

I thought that the directions given made use of your ISP's (caching) DNS servers rather than going directly to the "root" authoritative servers. Thus if the ISP has it cached, you would get that info. Otherwise, what was the point of editing the files to include the ISP's DNS addresses?

[ Reply to This | # ]

Irresponsible? I don't think so...
Authored by: cynikal on May 05, '05 09:16:39AM

i stand corrected, i didn't look too deeply into his instructions, just saw him starting up bind to be used locally.. but if you're still depending mostly on your isp's dns servers, then this hint is pretty useless since they're likely the weakest part of the lookup chain.

actually if you use a nat device's dns (a nat device meaning a dsl/cable modem or wireless router), you can speed your initial lookups up by telling the nat to use a faster dns server.. i'm on verizon's dsl and the default dns server was dog slow, but i did some looking around and found a way faster one that was less hops away too.



[ Reply to This | # ]