Hi there, you are definitely right to change all the zones to AD integrated
as that will definitely help and reduce complexity. On an internal LAN you
dont need reverse lookup zones as they wont be used unless you are using a
specific application that uses reverse dns for security reasons.
James.
--
James Yeomans, BSc, MCSE
"JMcB" wrote:
[Quoted Text] > Inherited DNS system with each of the DC-DNS servers were setup differently
> (primary, secondary, etc). We have the following setup:
> Site1: domain controllers with DNS; DHCP server. No errors in DHCP logs.
> Site2: domain controllers with DNS
> Site3: domain controllers with DHCP, no DNS. No errors in DHCP logs.
> Site4: domain controllers with DHCP, no DNS. Errors in DCHP "DNS Update
> Failed"
> Bandwidth isn't an issue.
> Subnets--numerous going into either Site1 or Site2.
>
> They have all been changed to AD integrated--will this correct the various
> primary/secondary configurations out there? If not, can they be easily
> changed and how.
>
> Reverse Lookup Zones
> Should I have one for each subnet, even if they don't have a DC (within
> reason, i.e. 172.26.9 and 172.26.8 could be 172.26.0.0)?
>
> DHCP & DNS--getting errors--related to Reverse Lookup zones? We're seeing a
> lot of "DNS Update Failed" in our DHCP logs.
>
> I've been spending the last couple of weeks re-learning MS-DNS, but am
> unsure as to where to start with some of these issues.
> --
> JMcB
|