Hi folks, I have some wierd Bind 91.3 problems ...... I've installed SuSE 7.3 Pro on an rackmount box with 2 Intel CPU's am having named problems with the reboot. When I do things manually the name service works fine. Iv'e tested it and all is great. But when I reboot the box, the resulting name service seems to hang.
From a security standpoint, I've limiting the transferrs, but this should not cause a problem.
Another anomoly I've seen is that named spawns 5 processes at the onset of things as does the name service cache daemon. Is this due to having 2 CPU's. Interrogating the /etc/logs/messages files articulates that named is indeed using 2 CPU's? Does bind 9X auto detect the use of two CPU and adjust things accordingly? Any clues to the vulnerability issues regarding this? Any idea of why the reboot would have named hang for processes like nslookup but when I stop and restart the server via rcnamed all is well and nslookup tests work properly? Many thanks in advance! ;-) -matt -- #################################################### Matthew R. Versaggi, Founder & President Versaggi Information Systems, Inc. Adjunct Professor of eBusiness DePaul University Email: mailto:matt@versaggi.com URL: http://www.dpu-ebiz.org (Academic 1) URL: http://www.dpu-ebiz.net (Academic 2) URL: http://www.dpu-ebiz.com (Academic 3) ####################################################