Re:RE: update so late!!

[mstk_a at livedoor.com]

>Your system is working perfectly.
>
>There is a wanted delay between the updates and the updating of the 
serial
>number.
>Also the .ixfr files are written only once an hour into the actual 
database
>file. This is intended.
>
>Burkhard Weeber
>viastore systems GmbH
>P/O Box 300668
>D-70446 Stuttgart
>Email: B.Weeber at viastore.de
>
>
>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
>Behalf Of mstk_a at livedoor.com
>Sent: Tuesday, December 19, 2000 11:54 AM
>To: bind-users at isc.org
>Subject: update so late!!
>
>
>
>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 .
>
>Any help will please . If you need more imfomation, I'll send.
>
>Thanks,
>
>                                 Masataka
>

Thank you for your quick reply.
And I'm so sorry that my posting is very difficult to read on the 
webpage (not begin new line).


I want to help next problem.
When I managed secondary name server(volvo : on this host, DHCP worked 
too), that time of delay updating occured complication.

My secondary name server is bind 9.1.0-b1 .


Primary name server send a zone forwarding message to secondary at the 
same time of logs'last comment([END DELTA]and[INCR_SERIAL]) appearance  
in db.ixfr/db.log. And it was made jounal files (knet.db.jnl, 
192.168.1.db.jnl) in /var/named of secondary.

  
And then secondary's db files(knet.db, 192.168.1.db) are changed these 
serial number .
While updating haven't finished ,  serial number only incremented, 
but not updated zone database.

Besides primary's zone db file have finished updating, but not send 
forwarding messeges to secondary. And secondary don't send request 
messages ,too. Because serial number has already changed newest one.


This is why?
Please advice for me.


Thanks,


        Masataka





  



___________________________________________________ 
100% FREE INTERNET ACCESS! http://www.livedoor.com/