Re: [cobalt-users] DNS gone haywire

[Dom Latter <qube@xxxxxxx>]

Jeff Lasman wrote:
> 
> At 10:10 AM 12/21/99  Dom Latter wrote:
> 
> >Hi all,
> >
> >I've turned on DNS on my Qube 2700WG to provide local resolution. [1]
> >However it is now generating huge amounts of network traffic
> 
> What's "huge" mean?

About ten queries per second.  This has now been resolved - by rebooting.
Now that's a first for me.  I just don't think to "fix" the Qube by 
rebooting.

> If you're just using local DNS to resolve your locall-hosted domains it
> shouldn't generate any network traffic at all.  However, if you use your
> local DNS for your users, then every time they try to get to an address
> they've never gone to before or an address who they have gone to before,
> but whose dns record in your cache has expired, there will be traffic to
> the root servers.  That's just the way DNS works.

All Clues gratefully received.

It's like this: our upstream provider is providing primary DNS for us.
What I've been doing so far is using a local Linux box to provide local
DNS, e.g. resolving 193.123.235.212 into dogbert.san.com (my NT box).
All the local Windoze machines are set up to query firstly the local 
DNS box and failing that to move on to our ISPs, for resolving other
domains.

I don't particularly want the whole world to be able to resolve anything 
in san.com apart from www.san.com.

The box doing that job is being retired, so I thought I'd move local 
DNS on to our Qube.  Which is whe problems started.

I've now got the IP of the ISP's DNS server entered as Primary, via 
the Qube's web interface, and the Qube itself as the secondary server.
Is this what I want?

Any guides to DNS on the web that explain everything in "Janet & John" 
language?
regards
Dom