update so late!!

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Tue Dec 19 13:16:34 UTC 2000


> 
> Hi, all.
> 
> I have a problem with dynamic updating.
> I use "dhcpd3.0b2 pl 11" and "bind8.2.2 pl 5".
> This is a log of when dhcpd(volvo) leases an IP for dhcp client
> (yongala),
> 
> >Dec 16 22:52:16 volvo dhcpd: delete IN A yongala.knet: succeeded.
> >Dec 16 22:52:16 volvo dhcpd: delete IN PTR 145.1.168.192.in-addr.arpa: 
> succeeded
> >Dec 16 22:52:16 volvo dhcpd: if IN A yongala.knet doesn't exist add 
> 1800 IN A yongala.knet 192.168.1.145: succeeded.
> >Dec 16 22:52:16 volvo dhcpd: delete IN PTR 145.1.168.192.in-addr.arpa 
> add 1800 IN PTR 145.1.168.192.in-addr.arpa yongala.knet: succeeded.
> >Dec 16 22:52:16 volvo dhcpd: DHCPREQUEST for 192.168.1.145 from 
> 00:a0:24:c9:c3:fa (yongala) via eth0
> >Dec 16 22:52:16 volvo dhcpd: DHCPACK on 192.168.1.145 to 
> 00:a0:24:c9:c3:fa (yongala) via eth0 
> 
> And then, dhcpd send update messages for named (kabu2000).
> Named creates knet.db.ixfr, knet.db.log, 192.168.1.db, and 
> 192.168.1.db.log.
> 
> ----knet.db.ixfr
> >;BIND LOG V8
> >[DYNAMIC_UPDATE] id 5074 from [192.168.1.20].1026 at 976975453 (named 
> pid 5877):
> >zone:   origin knet class IN serial 2000121601
> >update: {add} yongala.knet. 1800 IN A 192.168.1.145
> >update: {delete} knet. 86400 IN SOA kabu2000.knet. root.kabu2000.knet. 
> ( 2000121601 1800 900 604800 86400 )
> >update: {add} knet. 86400 IN SOA kabu2000.knet. root.kabu2000.knet. ( 
> 2000121602 1800 900 604800 86400 )          
> >[END DELTA]
> 
> ----knet.db.log
> >;BIND LOG V8
> >[DYNAMIC_UPDATE] id 5074 from [192.168.1.20].1026 at 976975453 (named 
> pid 5877):
> >zone:   origin knet class IN serial 2000121601
> >prereq: {nxrrset} yongala.knet. IN A
> >update: {add} yongala.knet. 1800 IN A 192.168.1.145
> >[INCR_SERIAL] from 2000121601 to 2000121602 Sat Dec 16 23:09:13 2000 
> 
> These logs'last comment([END DELTA]and[INCR_SERIAL]) appear a few 
> minutes later. I think these comment show the end of updaing, but db 
> files(knet.db and 192.168.1.db) are updated actually half an hour later.
> I can't undestand why .

	Because it takes less resources to just record the update
	/ changes than it does to re-write the zone file for every
	update.  If you delay the write several update are consolidated
	into one re-write.

	Mark

> 
> Any help will please . If you need more imfomation, I'll send. 
>  
> Thanks,
> 
>                                  Masataka
> 
> ___________________________________________________ 
> 100% FREE INTERNET ACCESS! http://www.livedoor.com/ 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com



More information about the bind-users mailing list