dynamic update...

[Mark.Andrews at nominum.com]

	It's usually just that the prerequisite conditions were not met.

	Mark
> 
> If you search the archives of this list you should find some messages regardi
> ng this that say it could be Windows 2000 might be doing secure updates that 
> aren't compatible with BIND, or that it is a standing bug in BIND 8.2.* (this
>  is all from memory).  
> 
> My dynamically updated zone files all have permissions of 444 and it is worki
> ng fine.  Perhaps there is a configuration error somewhere preventing the upd
> ates?
> 
> -----Original Message-----
> From: Jeff Bowers [mailto:jbowers at bsat.com]
> Sent: Wednesday, October 25, 2000 8:48 AM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: dynamic update...
> 
> 
> I have two odd symptoms on a dynamic update box.  this is running for our
> rollover to win2000
> 
> first:  I get (in /var/adm/messages) the vague ...
> 
> "Oct 25 09:44:00 pebble named[587]: error processing update packet id 7122
> from [90.132.162.231].3763"
> 
> the IP address is the new global controller.  it is in the acl to allow
> updates. check name errors is off.
> 
> the other, possibly related problem is that after updating a db file in
> /var/name, (in this case the db.msdcs and subnet rev tables) it chmods that
> file to a 444.  chmod'ing it back to a 644 lets it then update.  the
> db.msdcs.log in this case states a rollup of the serial counter that is not
> in the SOA record.
> 
> Even the third edition BIND book doesn't even come close to describing this.
> 
> Box is a Sparc Ultra 5 running Solaris 2.7
> 
> 
> 
> 
> 
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com