DNS Server Cache

  • Thread starter Thread starter JBFields
  • Start date Start date
J

JBFields

I've been assuming that a caching server clears its cache when
rebooted. Dawns on me that i"ve not actually read anywhere
authoritative saying so. Does it?
 
JBFields said:
I've been assuming that a caching server clears its cache when
rebooted. Dawns on me that i"ve not actually read anywhere
authoritative saying so. Does it?
Click to expand...

Yes. And when restarted.

[One of the irritating limitations of the Windows DNS
server is that there is no way to reload the cache from
a file at startup.]

Also note that the "server cache" is completely independent
of the "DNS Client" service cache on DNS clients, including
even a DNS server which runs this slightly misnamed process.

The DNS Client service should likely have been named the
"DNS Cache client" -- DNS still works when it is not running.
 
Herb said:
JBFields said:
I've been assuming that a caching server clears its cache when
rebooted. Dawns on me that i"ve not actually read anywhere
authoritative saying so. Does it?
Click to expand...

Yes. And when restarted.

[One of the irritating limitations of the Windows DNS
server is that there is no way to reload the cache from
a file at startup.]

Also note that the "server cache" is completely independent
of the "DNS Client" service cache on DNS clients, including
even a DNS server which runs this slightly misnamed process.

The DNS Client service should likely have been named the
"DNS Cache client" -- DNS still works when it is not running.
Click to expand...

Actually Herb, the true Service name is Dnscache. The GUI calls it the DNS
client. But to stop it and start it from a command it is net stop Dnscache &
net start dnscache
 
The DNS Client service should likely have been named the
Actually Herb, the true Service name is Dnscache. The GUI calls it the DNS
client. But to stop it and start it from a command it is net stop Dnscache
&
net start dnscache
Click to expand...

Well, technically it's not a GUI issue but rather the
display name displayed and used by both the GUI and
the command line "Net Start" (net stop) command.

Try "net start" for the display, and you can start and
stop it by that name as well.

In any case, the (display) name is a terrible choice
that has continued to confuse people.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Kevin D. Goodknecht Sr. said:
Herb said:
JBFields said:
I've been assuming that a caching server clears its cache when
rebooted. Dawns on me that i"ve not actually read anywhere
authoritative saying so. Does it?
Click to expand...

Yes. And when restarted.

[One of the irritating limitations of the Windows DNS
server is that there is no way to reload the cache from
a file at startup.]

Also note that the "server cache" is completely independent
of the "DNS Client" service cache on DNS clients, including
even a DNS server which runs this slightly misnamed process.

The DNS Client service should likely have been named the
"DNS Cache client" -- DNS still works when it is not running.
Click to expand...

Actually Herb, the true Service name is Dnscache. The GUI calls it the DNS
client. But to stop it and start it from a command it is net stop Dnscache
&
net start dnscache
Click to expand...
 
Back
Top