Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

named



On Nov 30, 2010, at 7:28 AM, Cole Tuininga wrote:
> 
> I'm a bit confused what you're trying to accomplish here.  The only 
> reason I can imagine for putting your own caching resolver between you 
> and the ISP resolver is if you wanted to override the records for a 
> particular zone for some reason.

You don't put your own resolver between you and the ISP's resolver.  You bypass the ISP entirely.  That's the point.  The only reason to rely on the ISP's resolvers is if you are unwilling or unable to run your own.  If you do run your own then you point it at something authoritative, i.e., one or more of the root name servers plus anything relatively local, such as a department at a university using the university's own resolvers.  Use of an intermediary puts you at the mercy of their overriding of authoritative records such as Comcast's and Verizon's "helpful" DNS redirects.

--Rich P.






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org