Help: "update failed" in debug log for Bind 8.2.2

[Jason]

Hi

I'm having a really irritating problem at the moment.  I have one dns server
which periodically fails to resolve hosts in one specific domain,
chipcenter.com.  I turned on debugging, and when the problem appears, I do
`nslookup www.chipcenter.com`, and this appears in the log:

XX+/127.0.0.1/www.chipcenter.com/A/IN
req: nlookup(www.chipcenter.com) id 33516 type=1 class=1
req: found 'www.chipcenter.com' as 'chipcenter.com' (cname=0)
sysquery: send -> [198.41.3.38].53 dfd=4 nsid=16366 id=0 retry=976569784
sysquery: send -> [198.41.3.38].53 dfd=4 nsid=23932 id=0 retry=976569784
forw: forw -> [198.41.3.38].53 ds=4 nsid=30015 id=33516 7ms retry 4sec
datagram from [198.41.0.4].53, fd 4, len 103
ncache: dname localhost, type 1, class 1
datagram from [198.41.3.38].53, fd 4, len 127
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16366
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;;      ns.chipcenter.com, type = A, class = IN
CHIPCENTER.COM.         2D IN NS        NS.DIGISLE.NET.
CHIPCENTER.COM.         2D IN NS        NS1.DIGISLE.NET.
NS.DIGISLE.NET.         2D IN A         167.216.128.33
NS1.DIGISLE.NET.        2D IN A         167.216.128.34
update failed CHIPCENTER.COM 2

followed by this repeating a few times (alternating between ns.chipcenter.com
and ns1.chipcenter.com):

resp: nlookup(ns1.chipcenter.com) qtype=1
resp: found 'ns1.chipcenter.com' as 'chipcenter.com' (cname=0)
datagram from [198.41.3.38].53, fd 4, len 128
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30015
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;;      www.chipcenter.com, type = A, class = IN
CHIPCENTER.COM.         2D IN NS        NS.DIGISLE.NET.
CHIPCENTER.COM.         2D IN NS        NS1.DIGISLE.NET.
NS.DIGISLE.NET.         2D IN A         167.216.128.33
NS1.DIGISLE.NET.        2D IN A         167.216.128.34
update failed CHIPCENTER.COM 2


if I grep for "update failed" in the log, it appears hundreds of times for
chipcenter.com, and a couple of times for one other domain.  If I stop and
restart named, I can start resolving chipcenter.com again.  This dns
server is not a primary or secondary for this domain.

Any ideas?

-- 
Jason Burnett  
jason at jnj.org      
That which does not kill me postpones the inevitable.