The servers use static mappings to the same external DNS servers.
During the PDC upgrade, you install DNS because DCPromo tells you to.
However, the parts which need to be done at the registrar would need to be done by you or the domain owner, and if you need any help with those steps, you would need to ask the registrar for assistance.
For our example, let's say these are the nameservers we are creating: Since this step is done within the server, we can do it for you if you open a Support Ticket and let us know the names and IP addresses you would like to use for the new nameservers.
When creating new nameservers, the general process is as follows.
The member computers don’t know that the domain has been upgraded to AD unless they just happen to authenticate at the PDC. Users treat additional keystrokes as if they were penalties visited upon them by uncaring IT bureaucrats. The resolver obtains this DNS suffix from one of several places.
The other computers get no group policies, so you can forget about any carefully-orchestrated centralized management scheme. Imagine what would happen if you asked your users to type Fully Qualified Domain Names (FQDNs) rather than simple flat names to connect to internal servers. Users are willing to type com to buy a used wristwatch, but they don’t want to type \w2k3s102school.edu\ freshman_zclass to map a drive. The domain to which the desktop or server belongs has a DNS name as well as a flat name.
DNS servers, however, stubbornly insist that every query specify a target domain. You can see this suffix in the Properties of the local system (Figure 1).
If you’re an experienced Windows system engineer, they may seem a little trivial.
But even the most highly trained and savvy administrator can get in a hurry and make a mistake.