Looking at Cache

[Mektub]

On Tue, 04 May 2004 22:32:15 +0100, Mektub
<jl.mektubDE_LE_TE_ME at web.de> wrote:

>On Tue, 4 May 2004 13:44:29 -0500, "Matt" <nospam.hciss at yahoo.com>
>wrote:
>
>>> >> rndc dumpdb
>>>
>>> > Does not work.  Tried it on my other Linux box running as an email
>>server
>>> > and it works there.  Is there a setting somewhere I could have =3D
>messed up
>>> > causing it to not cache?
>>>
>>> > Matt
>>>
>>> *what* does not work ? Does 'rndc' give an error ( faulty
>>> rndc/key setup) ?  Or don't you find the file ( you can
>>> specify where it will go to ; options dump-file :
>>> "dump-file
>>
>>My bad.  Did not really explain that well at all.
>>
>>I do "rndc dumpdb" and it returns instantly.  According to "rndc =
--help"=3D
> its
>>supposed to dump this to "named_dump.db".  So after the "rndc dumpdb" I=
 =3D
>do
>>"locate -u" then "locate named_dump.db" and it finds no such file.  I =3D
>try
>>this same procedure on my linux email server running bind/named and it
>>outputs the dump file where its supposed to be with about a ~meg of =
data=3D
> in
>>it.
>>
>>So I think somehow it much not be caching.  The DNS lookup part does =3D
>work
>>though so I assume its just not caching.
>>
>>Matt
>>
>>>     The pathname of the file the server dumps the database to when
>>instructed to do so with rndc dumpdb. If not specified, the default is
>>named_dump.db."
>>
>>
>
>It happened to me also, it returned instantly. I am using bind as a
>caching only nameserver.
>
>I had to explicitely put in options in /etc/named.conf the entry:
>
>dump-file "/tmp/DnsDump";
>
>after that it started dumping the cache.
>
>regards,
>
>Mektub

Hit return to soon. The problem was with the /var/named directory
permissions/ownership

Mektub