Tim wrote:
On Sat, 2007-04-28 at 10:54 -0400, Bob Goodwin - W2BOD wrote:
Is there a file I can examine that will show me what URL's are
presently cached in my caching-nameserver ?
FQDNs, not URIs, as Bruno pointed out. But check out the "rndc"
command. That man file for it is lacking, but running the command
without any parameters produces this:
# rndc
Usage: rndc [-c config] [-s server] [-p port]
[-k key-file ] [-y key] [-V] command
command is one of the following:
reload Reload configuration file and zones.
reload zone [class [view]]
Reload a single zone.
refresh zone [class [view]]
Schedule immediate maintenance for a zone.
retransfer zone [class [view]]
Retransfer a single zone without checking serial number.
freeze zone [class [view]]
Suspend updates to a dynamic zone.
thaw zone [class [view]]
Enable updates to a frozen dynamic zone and reload it.
reconfig Reload configuration file and new zones only.
stats Write server statistics to the statistics file.
querylog Toggle query logging.
dumpdb [-all|-cache|-zones] [view ...]
Dump cache(s) to the dump file (named_dump.db).
stop Save pending updates to master files and stop the server.
stop -p Save pending updates to master files and stop the server
reporting process id.
halt Stop the server without saving pending updates.
halt -p Stop the server without saving pending updates reporting
process id.
trace Increment debugging level by one.
trace level Change the debugging level.
notrace Set debugging level to 0.
flush Flushes all of the server's caches.
flush [view] Flushes the server's cache for a view.
flushname name [view]
Flush the given name from the server's cache(s)
status Display status of the server.
recursing Dump the queries that are currently recursing (named.recursing)
*restart Restart the server.
* == not yet implemented
Version:
Note the "dumpdb" information, around about the middle. There's also
statistics options which give you a summary about what it's got, without
masses of explicit detail.
Tim:
rndc dumpdb -cache Produces a lot of data in
/var/named/chroot/var/named/data/cache_dump.db. It looks interesting
and seems to be related to places I have been so I assume that it is
either what is in the nameserver cache when the command was given or is
it a history of what has been?
And then the notation "ttl" I assume is time to live for that record, is
it expressed in seconds or some arbitrary unit peculiar to the
computer? Where is the ttl value assigned, by the creator or is it a
value determined in this computer?
"Unassociated entries" Is it caching addresses that were received in
numeric form?
I'm sure there are many questions, some will yield to google I suppose ...
Thanks.
Bob Goodwin
--------- --------- --------
; cbru.br.ns.els-gms.att.net [v4 TTL 39566] [v4 success] [v6 unexpected]
; 199.191.128.105 [srtt 12] [flags 00000000] [ttl -7638]
; udns1.ultradns.net [v4 TTL 39688] [v4 success] [v6 unexpected]
; 204.69.234.1 [srtt 333975] [flags 00000000] [ttl -44908]
; C.ROOT-SERVERS.NET [v4 TTL 37456] [v4 not_found] [v6 unexpected]
; 192.33.4.12 [srtt 6676070] [flags 00000000] [ttl -43329]
; M.ROOT-SERVERS.NET [v4 TTL 37456] [v4 not_found] [v6 unexpected]
; 202.12.27.33 [srtt 6542549] [flags 00000000] [ttl -43329]
;
; Unassociated entries
;
; 64.233.179.9 [srtt 1493225] [flags 00000000] [ttl 1321]
; 209.85.139.9 [srtt 1651330] [flags 00000000] [ttl 1321]
