Dear Junior Admin,
PCs generally have an eight day default lease period. The PC will not make contact to the DCHP server again until halfway through the lease time. Since you changed the scope on Friday, the PCs that just renewed a lease will not contact the DCHP until Tuesday. You may force the PCs to grab new IP addresses by opening a DOS prompt, and do an “ipconfig/release” and an “ipconfig/renew” on each computer.
If the problem still isn’t solved, check your scope configuration, and make sure the network/subnet mask match what is configured on the router that is connected to this local LAN.
Terra Klaase
IT Admin
PART B
Dear Junior Admin,
Active Directory integrated zones must be hosted by Domain Controllers (DCs), and all Active Directory integrated zones are primary zones. Given this, we’re really talking about where to place Domain Controllers servicing the additional role of DNS server.
Determining where to place DCs/DNS servers isn’t always straight-forward. However, as a rule of thumb, I take the view that any branch location that’s going to be utilize Active Directory services (authentication, file services, etc.), benefits from having a local DC and domain-integrated DNS services.
You might already know much of this, so bear with me…
When deciding where to place DC/DNS Servers, keep the following things in mind:
* Domain members rely heavily on DNS services to locate domain resources. For example, when a domain-joined computer boots, it queries domain Service Locator records (SRV) in DNS to locate a Domain Controller against which to authenticate. Without a local DNS instance, this process has to take place over a potentially slow site link. Of course, once a computer has located a Domain Controller, it will continue to authenticate against that server until it something forces the client to find another DC.
* Over a slow link, the regular activities of authenticating against remote DCs, querying domain resources, and