Re: caching only server?
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 10 Apr 2005 01:46:10 -0500
"Dan" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:095001c53c65$48fab300$a501280a@xxxxxxxxxx
> I hear a lot of hub-bub when people talk about DNS on
> bind about "caching only" servers.
A caching only DNS server is just a name commonly used
for a DNS server which simply has no zones of it's own.
This contrasts with a DNS Server which does have zones
of it's own defined -- i.e., a DNS Server which is 'authoritative'
for one or more zones.
In some sense (but not in common terminology), probably the
majority of DNS servers are caching servers, since even if
they hold zones many of them are quite able to cache information
they obtain from other DNS servers (on their cliedts' behalf.)
> Is this a real option in Windows?
Sure. Install DNS service (defaults) and create no zones.
Voila! A caching only server.
Configure it to resolve the addresses you need by querying
other DNS servers (recursion or forwarding) and it is a
"caching only DNS server".
> If I have a server running DNS, and it
> houses an ADI zone for my internal domain/forest and a
> user requests something for another zone that my DC has
> to go get will it be cached automatically with no
> additional configuration or do I need to tell it to cache
> certain types of things?
The default is to cache. One some servers that may be
disabled but this is seldom if ever a useful step.
The most common place to purposely use a "caching only
server" is at your firewall or within your DMZ.
All other DNS servers inside your network would then
be configured to "forward" to this server so that it is
the only DNS server that passes the firewall and thus
protects your important internal DNS servers which may
be holding not only sensitive information, but also be
doing other sensitive jobs like Domain Controller.
The caching only server in this example becomes (also)
a "forwarder."
Many people thus confuse "forwarders" and "caching-only"
since sometimes they are the same DNS server, sometimes
they use each other to resolve additional names.
The key here is that these are conceptual definitions as much
as they are technical.
The server to which we forward is a "forwarder" (and it
doesn't even know it.)
Most servers do caching -- if they have no zones, they are
"caching only."
.
- References:
- caching only server?
- From: Dan
- caching only server?
- Prev by Date: Re: DNS Foward Lookup Zone
- Next by Date: Error - The directory service is busy
- Previous by thread: Re: caching only server?
- Next by thread: Really strange DNS problems
- Index(es):
Relevant Pages
|
