[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] [QUBE2] Using the Qube's DNS server as a caching nameserver
- Subject: [cobalt-users] [QUBE2] Using the Qube's DNS server as a caching nameserver
- From: <rpaiz@xxxxxxxxxxxxxx>
- Date: Wed Sep 13 18:43:14 2000
This is a topic on which I am simply ignorant. It is not, strictly speaking,
a Cobalt issue, but I'm lost and could use pointers to documentation or a
little help.
I understand that a nameserver can be configured to run recursive queries.
That is, I could in theory have only a single nameserver configured via
DHCP. Then, when a DNS query was received, the server would determine
whether it could answer the query authoritatively or not. If not, then the
server would itself go out to another nameserver and search for the answer.
Having found the answer, the server would return it to the client and cache
it for future use.
This would allow the client to only know the address of one nameserver, and
then I can setup the Qube to search for the answers as best it can. Can this
be done with a Qube? Where would I go to find out how?
--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>