Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a 'named' service running on a database server that is currently not being used. I am getting dozens of "network unreachable" errors in the messages log every day from named, presumably from people looking for common exploits on the box. Do I even need to be running the named service? Or is there something else I should do to cut down on log spam? This box will only be used to serve database queries. (Note: I know there is no real reason for this box to be directly connected to the internet, but that is the current configuration. So go ahead and tell me to put it behind a firewall, I already know that.)

share|improve this question
up vote 1 down vote accepted

Are you using this server to provide DNS services? (doesn't sound like it) If not, then you can surely shut down named.

share|improve this answer
...and remove the local resolver from /etc/resolv.conf if it's in there. – voretaq7 Feb 28 '11 at 21:04
That is what I'm planing to do, only now I need to point the db server somewhere else for DNS. – Roger Halliburton Feb 28 '11 at 22:31

If you don't need to resolve many hostnames on the server then you can just put the ones you need in the /etc/hosts file and disable named.

share|improve this answer

If your own IP address or is not listed in /etc/resolv.conf, go ahead and shut it down.

And, yes, at a minimum configure iptables to block everything except authorized users. Yikes.

share|improve this answer
Actually yes it has both and the external ip. But, long story short, I have shut it down. – Roger Halliburton Feb 28 '11 at 22:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.