DNS issue, web hosting server, standard primary zones in AD
Posted on 2003-02-23
I have posted on this project I inherited last week and I would like to kick it arounf again.
Just to refresh, I am working on a Small Business Server 2000 box that is being used as a web hosting server and also a primary DNS server. The server (NS1) is a member of the os.triaxdesign.com domain and there is an Active Directory integrated forward lookup zone called os.triaxdesign.com.
In DNS, there are about twenty independent domains being hosted that have standard primary forward lookup zones created. I asked last wek if it was OK that the hosted domains, that are not child domains, be standard primary.
Here's the clincher. A standard primary domain has been created called triaxdesign.com and this is also the DNS server. An alias has been created called NS1 in this zone. This zone, plus all the zones from the hosted domains, have an NS entry in their zone that points to NS1.triaxdesign.com. These in turn point to os.triaxdesign.com so that they are one in the same.
What occurred to me is that all the domains have the entry NS NS1.triaxdesign.com and that this has to be resolved each time. Would it not be more efficient to make all the standard primary zones, active directory integrated to store this information in the AD database?
When I originally asked the question about whether it was OK that these remain standard primary, the OK was based on the fact that they are all independent domains. however, they all use the same NS that is also the SOA for each domain.
Should I change the domains being hosted to AD?