[SunHELP] DNS issue

Luc I. Suryo luc at suryo.com
Sat Dec 20 01:22:05 CST 2003


Lara,


I bet thsi is a setup in your rndc-key and some 'error' in the
named.conf, however I would advice to move to a newer version of bind!

the 'think' is that you need to communicate with rndc in bind 9 to
control things in bind and will need to setup acl/key.. all in the
documentation (www.isc.org)

and in case you 'lazy' check ftp.patriots.net the pacakeg come with
several scripts and example that should make your live easier
(automatically increase the serial and so).. we using this package on
several system (8 systems) and like it :) 


sorry of not a big help...


-ls

Lara Matthews <lara.matthews at accesscomputing.co.uk>
   wrote at Fri, Nov 21, 2003 at 11:46:04AM +0000:

> Hi Guys
> 
> I wonder if anyone can help.
> 
> I have a problem with my DNS server it is constantly coming back with 
> the error
> 
> Nov 17 06:01:16 nsaccess /usr/local/sbin/named[5254]: [ID 866145 
> daemon.error] client 194.130.253.16#4578: update denied
> Nov 17 06:06:25 nsaccess /usr/local/sbin/named[5254]: [ID 866145 
> daemon.error] client 194.130.253.16#4591: update denied
> Nov 17 06:06:28 nsaccess /usr/local/sbin/named[5254]: [ID 866145 
> daemon.error] client 194.130.253.16#4601: update denied
> 
> Also daemon seems to fall over on a regular basis.  I have no idea if 
> these two activities are related.  I just tried to update our primary 
> config file with a new serial number incase we are out of date and I got
> 
> Nov 21 11:35:30 nsaccess /usr/local/sbin/named[7901]: [ID 866145 
> daemon.notice] starting BIND 9.1.3rc1 -u named
> Nov 21 11:35:32 nsaccess /usr/local/sbin/named[7901]: [ID 866145 
> daemon.error] client 194.130.253.16#4758: update denied
> Nov 21 11:40:21 nsaccess /usr/local/sbin/named[7901]: [ID 866145 
> daemon.error] client 194.130.253.16#4781: update denied
> Nov 21 11:40:28 nsaccess /usr/local/sbin/named[7901]: [ID 866145 
> daemon.error] client 194.130.253.16#4793: update denied
> 
> but the daemon is still running.  Any suggestions why this might be 
> happening?



More information about the SunHELP mailing list