RE: how to view cached lookups - bind 9.2.3??

I believe you need to do a "rndc dumpdb". Then you will find a =
"named_dump.db" somewhere in your directory structure. I think it =
defaults to whatever you specified with the "directory" option in the =
config.

Then you'll see things like this in the file:

snm.cngb.com. 54577 A 203.93.18.5
; glue
cntfl.com. 153759 NS dns.sprintans.net.
153759 NS server.cntfl.com.
; answer
server.cntfl.com. 153759 A 199.44.2.10
; glue
cobaltgroup.com. 149102 NS ns1.cobaltgroup.com.
149102 NS ns2.cobaltgroup.com.
; answer
ns1.cobaltgroup.com. 149102 A 216.231.224.13
; answer
ns2.cobaltgroup.com. 149102 A 216.231.224.12
; additional
cogentco.com. 135285 NS auth1.dns.cogentco.com.
135285 NS auth2.dns.cogentco.com.
135285 NS auth4.dns.cogentco.com.
135285 NS auth5.dns.cogentco.com.

-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org]On
Behalf Of John Smith
Sent: Tuesday, December 28, 2004 10:08 AM
To: comp-protocols-dns-bind@isc.org
Subject: how to view cached lookups - bind 9.2.3??


Is there a way to view what addresses are cached (from recursive
lookups) using bind 9.2.3?


TIA




-----Message=20Disclaimer-----

This=20e-mail=20message=20is=20intended=20only=20for=20the= 20use=20of=20the=20individual=20or
entity=20to=20which=20it=20is=20addressed,=20and=2 0may=20contain=20information=20that=20is
privileged,=20confidential=20and=20exempt=20from=2 0disclosure=20under=20applicable=20law.
If=20you=20are=20not=20the=20intended=20recipient, =20any=20dissemination,=20distribution=20or
copying=20of=20this=20communication=20is=20strictl y=20prohibited.=20If=20you=20have
received=20this=20communication=20in=20error,=20pl ease=20notify=20us=20immediately=20by
reply=20email=20to=20Connect@principal.com=20and=2 0delete=20or=20destroy=20all=20copies=20of
the=20original=20message=20and=20attachments=20the reto.=20Email=20sent=20to=20or=20from=20the
Principal=20Financial=20Group=20or=20any=20of=20it s=20member=20companies=20may=20be=20retained
as=20required=20by=20law=20or=20regulation.

Nothing=20in=20this=20message=20is=20intended=20to =20constitute=20an=20Electronic=20signature
for=20purposes=20of=20the=20Uniform=20Electronic=2 0Transactions=20Act=20(UETA)=20or=20the
Electronic=20Signatures=20in=20Global=20and=20Nati onal=20Commerce=20Act=20("E-Sign")
unless=20a=20specific=20statement=20to=20the=20con trary=20is=20included=20in=20this=20message.