lame server resolving - repeats 280 times

[Duane J. Von Lanken]

I am running HPUX 11.11 with Bind 9.2.0, this server is set up as a
caching only server and has approx 440,000 queries per 15 minutes.  I
recently started getting about 110,000 failed queries per 15 minutes. 
Usually they run on average about 10-12,000 per 15 minutes.  The CPU
has been spiking up to +90%, when it usually runs about 40-50%.  I am
getting in the log (lame server resolving
'chela.tower-hill.pvt.k12.de.us''  MASSIVE amount of times.  How can I
correct this?
THANKS!  


Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:38 ns1  above message repeats 85 times
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'vscan.mocaasap.com' (in 'mocaasap.com'?): 216.49.80.74#53
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'www.todoporaventura.com' (in 'todoporaventura.com'?):
66.199.248.202#53
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.4#53
Nov 23 10:53:38 ns1  above message repeats 280 times
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'www.todoporaventura.com' (in 'todoporaventura.com'?):
66.199.248.203#53
Nov 23 10:53:38 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.4#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'104.210.72.200.in-addr.arpa' (in '210.72.200.in-addr.arpa'?):
200.72.1.254#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'tvmedia.co.jp' (in 'tvmedia.co.jp'?): 211.134.181.104#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving 'pow.com' (in
'pow.com'?): 212.187.158.3#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'tvmedia.co.jp' (in 'tvmedia.co.jp'?): 211.134.181.105#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'104.210.72.200.in-addr.arpa' (in '210.72.200.in-addr.arpa'?):
200.72.1.253#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving 'pow.com' (in
'pow.com'?): 212.100.224.247#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.4#53
Nov 23 10:53:39 ns1  above message repeats 3 times
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.4#53
Nov 23 10:53:39 ns1 named[18839]: lame server resolving
'chela.tower-hill.pvt.k12.de.us' (in 'tower-hill.pvt.k12.de.us'?):
4.2.49.2#53