named

[colet-KCgK2vT7wad/90uGnh1m2w at public.gmane.org (Cole Tuininga)]

On 11/29/2010 10:29 PM, Stephen Adler wrote:
> I've been having trouble with verizon's domain name servers, so I
> decided to fire up a caching domain name server.

[snip]

> I then thought I should have my named query the verizon dns servers
> instead of hitting the root servers and when I did, I got a bunch of the
> following errors...

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.

I suggest that if you're going to use a caching resolver (especially one 
with DNSSEC turned on) that you go right to the root servers.

*Puts on his dyn.com employee hat*

However, if you're having trouble with your ISPs resolvers (much like 
Comcast subscribers a couple days ago), I recommend trying out dyn.com's 
Internet Guide service.  Simpler than running your own recursive, and 
you get a few nifty features for free.

http://www.dyndns.com/services/dynguide/

-- 
Cole Tuininga
Lead Developer
colet-KCgK2vT7wad/90uGnh1m2w at public.gmane.org