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

Re: [cobalt-users] DNS gone haywire



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?

through querying the root servers given in /etc/named/db.cache.
What's going on?  Any ideas?

Are you just using local DNS to resolve your locally-hosted domains for the world?

Or are you using local DNS to resolve DNS for your users who are surfing the web, using email, etc.?

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.

[1] We have a Class C subnet; user machines are configured with
firstly the Qube and then external machines as providers of DNS.

Hopefully your secondary isn't on the same subnet (more hopefully not even on the same network) as your primary; that kind of defeats the whole concept of having secondary DNS.

We host DNS both for websites and for ISPs' outgoing customer traffic, but we don't host it on our RaQs; they're a bit lightweight for the kind of heavy-duty DNS hosting we do.

Jeff