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 want to set up BIND for a private subdomain on a private network, like in the question here: How to configure bind for a private subdomain?

My question is this - should my (linux) router act as the DNS server for this? Or should I have a seperate machine on the network acting as the DNS server? Does it not matter as long as all the machines on the network are configured to resolve to the internal DNS server?

share|improve this question
up vote 3 down vote accepted

It doesn't matter where you run it as long as it is reachable from the internal machines.

DNS is a very lightweight service, which can easily coexist with many others on a machine.

However, make sure it keeps working. When DNS fails, dozens of things will stop working and you'll be wondering what the heck is going on before you figure out DNS is down.

share|improve this answer
Okay, thanks. I just didn't know if there was a "best" way to do this (or a standard to follow). – smcg Jun 7 '12 at 21:07
You're welcome. I expanded the answer a bit. – Martijn Heemels Jun 7 '12 at 21:09

On a small network I run dnsmasq on the router to provide DNS and DHCP services. It has the advantage of adding DHCP clients to DNS as well as using the /etc/hosts file as a source for local addresses. It is much simpler to configure than bind.

In either case DNS will require minimal resources. dnsmasq runs quite well on on OpenWrt router.

share|improve this answer

Run it on the router since it's Linux already it will be easy to install BIND. Routers are usually configured to serve DNS.

share|improve this answer

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.