Caching-only Name server does Zone Updates
Barry Margolin
barmar at alum.mit.edu
Tue Feb 3 08:42:32 UTC 2009
In article <gm8o6b$1vav$1 at sf1.isc.org>, "Ashish" <ashish.rao at wipro.com>
wrote:
> Thank you Mark,
>
> Doupdate is followed by lot of statements like
>
> Db_update
> Match
>
> Please see the content below.
> =========================================================================
> Doupdate(zone 0, savens x, flags y)
> Doupdate: dname 21.in-addr.arpa type 6 class 1 ttl 600
> Db_update(21.in-addr.arpa, 0x12345, 0x56789, 087, 0x76543) match(0x9b430, 1,
> 6) 1, 6
> db_update: flags = 0x19, sizes = 71, 71 (1)
> match(0x9123v, 1, 6) 1, 6
> db_update: flags = 0x19, sizes = 71, 71 (1)
> match(0x9sd33, 1, 6) 1, 6
> db_update: flags = 0x19, sizes = 71, 71 (1)
> match(0xdg6d8, 1, 6) 1, 6
> db_update: flags = 0x19, sizes = 71, 71 (1)
> match(0x6abde, 1, 6) 1, 6
> ==========================================================================
>
> Please correct me if I am wrong, I thought that for cache update it should
> update only one record. So why so many updates are been made.
The response probably contained NS records in the Authority Section and
the corresponding A records in the Additional Section. These update the
cache as well.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list