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

We run a mac network here in the office. We have an internal DNS server to manage the network. Everything is resolved to a local ip (for etc). However, we also have an external DNS server for when our users are not in the office. However, isn't it a pain to have to manage two lists? Whenever you change something you have to change another? And you can't have one be a slave of another because the ip are sometimes different (for example would point to a local ip in local dns server but an external ip in the external dns server). Any tricks?

share|improve this question

If you're running BIND on your public DNS server, you could configure it to perform what's known as "split DNS". This is where queries from one location get one set of responses, and queries from another location get another set of responses. Other DNS server implementations may support this as well, but there is an excellent howto for BIND which explains the details on how to configure it.

I'll amend that to say that when you configure BIND in this way, each "location" that you're splitting gets its own zone file, so you still have two lists to manage, but they're at least on the same server rather than different servers.

share|improve this answer

I am using djbdns because of this...

It is hard to get it first, but it works well.

share|improve this answer
I no longer recommend djbdns. It doesn't do DNSSEC, and it has security problems out of the box (go check the CVE database). – Mark Johnson Dec 25 '12 at 5:24

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.