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

dnsmasq is run to help make the user experience smoother for the desktop users. If I run bind/named on this same server will there be conflicts between the two? What are the limitations of dnsmasq, where I should use bind/named instead?

In particular, I've set up bind to run a psuedo-domain locally. It works, but I'm just curious to know if I should've done this through dnsmasq instead of running yet another service that seems to duplicate functionality.

share|improve this question
up vote 3 down vote accepted

By default you won't be able to run bind and dnsmasq simultaneously, because they will both try to bind to port 53 and one of the will fail. (It is possible to run them simultaneously if you configure them to bind to different IP addresses.) Based on what you want to accomplish, I would personally use dnsmasq instead of bind, because it's smaller and simpler. The main difference is that dnsmasq is not intended to be used as an authoritative nameserver, whereas bind is.

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.