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

In my DNS administration software I have a option to create a new DNS zone and option to add records to existing DNS zone that I use for my first domain.

I would like to add next doman in DNS. Should I put it into existing zone or create new one? I'm a beginner in DNS configuration so a little explanation here would be great.

share|improve this question
up vote 5 down vote accepted

You should have one zone per domain, so everything for domain1.tld would go in and entries for domain2.tld would go in (or wherever your specific software stores zones).

What seems like the exception is reverse DNS zones files, but they actually function the same way, just think of the domain being 192.168.1. So anything with a 192.168.1.x IP would go in and it could contain PTRs in domain1.tld & domain2.tld.

share|improve this answer
I see zero reason to create a zone per domain. Zones and domains are separate concepts, and there is nothing wrong in having several domains in a zone. – bortzmeyer Jan 22 '10 at 8:10
The OP is talking about administration software. A lot of these assume a single zone per domain so the answer seems good (enough) - but yes technically there's no reason to have one zone per domain. – Server Horror Jun 14 '11 at 17:44

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.