<div>
Honestly you and/or you admins are the only ones that can determine if those zones are needed. &nbsp;Are teh nameservers for those zones different than your three DNS servers? &nbsp;If so are the zones valid (in other words do records resolve for those zones i.e. <a href="http://www.little.xyzsb.org)?" rel="ugc">www.little.xyzsb.org)?</a><br />
<br />
You can look in your DNS logs (assuming you have logging enabled) to see if anyone is actually querying your DNS servers for those zones, or you can use netmon or wireshark to watch DNS traffic based on those zones.<br />
<br />
The last thing you want to do is delete a zone that you don't think is in use only to find out that it is in use resulting in a service outage.
</div>


Honestly you and/or you admins are the only ones that can determine if those zones are needed.  Are teh nameservers for those zones different than your three DNS servers?  If so are the zones valid (in other words do records resolve for those zones i.e. www.little.xyzsb.org)? [http://www.little.xyzsb.org)?]

You can look in your DNS logs (assuming you have logging enabled) to see if anyone is actually querying your DNS servers for those zones, or you can use netmon or wireshark to watch DNS traffic based on those zones.

The last thing you want to do is delete a zone that you don't think is in use only to find out that it is in use resulting in a service outage.

<div>
<div class="content wysiwyg-content">
I have three domain controllers running Win 2008 R2 with DNS. &nbsp;For some reasons, there are two sub zones under the Forward Lookup Zone. &nbsp;I dont think they belong there. &nbsp;Please refer to the diagram for explanation.<br />
<br />
As you can see from the diagram, there are two sub zones, little.xyzsb.org &nbsp;and super.xyzsb.org under each DNS server. &nbsp;Both zones have entries for nameservers and SOA.<br />
<br />
Are there any reasons I should not keep them?<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/05_w19/848466/dnszones.png" target="_blank" class="file-inline" title="dns zones (107 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>dnszones.png</a>
</div>
</div>


dnszones.png

I have three domain controllers running Win 2008 R2 with DNS.  For some reasons, there are two sub zones under the Forward Lookup Zone.  I dont think they belong there.  Please refer to the diagram for explanation.

As you can see from the diagram, there are two sub zones, little.xyzsb.org  and super.xyzsb.org under each DNS server.  Both zones have entries for nameservers and SOA.

Are there any reasons I should not keep them?

Confusion over Windows DNS Zones

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.