Not sure what has caused this error on my home linux server but you may have an idea...

I'm running RH 9 with the standard software version for this distro.

I hit some keys on the keyboard while i was moving some stuff over the weekend and managed to lockup the server. I had no choice but to do a manual power off and on again. Linux fixed the file system and continued to boot as normal but failed to start apache. Now i hadnt touced a thing and the knocking of the keys hadnt done something i dont think.

I tried to manually start the service and it still failed etc. i looked in /var/log/httpd/error_log and notcied it couldnt find the IPv4 name for custard and something about a unique id module. After looking about on the net i disabled that module in /etc/httpd/conf/httpd.conf and the service started OK and everything is fine once again.

But if i go to the command prompt and type just 'host custard' i get a 3(NXDOMAIN) error? I never used to... but if i type the fqdn it works fine as normal. I think something has been currupted in bind? but i havent touched a file for ages.

you might have an idea.

Thanks

Graeme.

Your /etc/resolv.conf is perhaps missing the

search

parameter.

i havent got a 'search' entry in there i dont think. never have before and it worked fine?

what does the search entry do?

Something i should mention is that i just installed a Watchguard Firebox II on the network and maybe the restart cause linux to request some new external info which is now getting blocked? not sure but my FW rules are fine. I'm not blocking anything i can see from this machine. I'm running my own BIND setup.

I cant see how this would be a firewall problem as the server would be doing a lookup against itself...

well i decided to look in my resolv.conf and i only had one line stating my nameserver... So i added a line to say domain cream-cake.com and it worked...

i also noticed that the machine wasnt remembering the domain name? so once i set that again it now knows it fqdn etc etc...

why i've had to add this line to the resolv when it worked before i'm not sure??

i re enabled the apache module and apache started up fine so it was def a bind type issue.

G