I liken it to the days when automobiles had carburetors; a mechanic could fix most engine performance problems by fiddling with the choke—spritz a little WD-40 into the throttle body, charge and retire in the suburbs after a few years. Check the TCP/IP settings, run a few utilities to verify the zone records, charge 0 (correcting for inflation) and retire to Arizona.
You’ll learn to identify the most common domain name system issues that cause problems for AD and Exchange and how to avoid them in the first place or isolate and resolve them if they occur in production.
Also, the more experience you have, the more likely you are to make your DNS infrastructure complex, inviting the attention of Mr.
Murphy and other elements of chaotic cosmic calamity. Each network interface has a set of TCP/IP settings that lists the DNS servers used by that interface.
To use it on Windows Server 2003, you need to install Support Tools from server’s CD#1 blog who is REAL genius in DNS topic.
His module for Power Shell is really great and very helpful.
But even the most highly trained and savvy administrator can get in a hurry and make a mistake.
This happens even though DHCP registered the record.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it. If you have Windows 2008 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.
Dynamic DNS is a feature that allows hosts to register their records in DNS, thus removing the need for administrators to manually create records.
In addition, Secure Dynamic Update can be required for zones that are Active Directory-integrated (and should be required, per best practices), which allows only members of the Authenticated Users group to register records.