We have a 2003 AD with our primary DNS on our DC and a secondary DNS (I just added) on another server. On our primary server, I have two forward lookup zones that I don't know if I need in addition to our main company.local zone...
_msdcs.company.local
company.lcl
_msdcs.company.local has several containers in it and a CNAME, NS and SOA record. Do I need this zone and if so, do I need to add it to my secondary server's Forward Lookup Zones? There is also an _msdcs object under company.local. It's a gray folder.
company.lcl has a bunch of A records in it and a NS and SOA record. Some of these records are static and other have various dates ranging from last year to a day ago. Do I need this zone or can I delete it? I don't know why some machines are creating these since our domain is company.local, not .lcl.
On my secondary DNS server, all of the zone records that transfered have static under timestamp even though most of these have a date and time on the primary DNS server. Is this ok?
Since I have two DNS servers now with one of them being a DC, I will configure each of their NIC properties to point to themselves as primary and the other as secondary. Is this correct? When I add the secondary DNS IP to the NIC settings and hit apply, will there be a short hiccop in network connectivity? One of these servers has file shares on it and the other is a print server so I wouldn't want to change the NIC properties if there is going to be momentary drop in network connections while users might be connected.