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.
Forward lookup zone not updating
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).
The TCP/IP Settings window calls this the Primary Suffix.
Without these records, a member computer can’t authenticate and get the information it needs to operate in the domain.
It then acts like a teenager who can’t get the car keys, growing sullen and exhibiting a variety of bad behaviors. Let’s say you’re a VAR with a customer you plan to upgrade from NT 4.0 to Windows 2000 Server or Windows Server 2003.
In the default suffix search configuration, a client in the west.school. If you want a flat name to resolve to the host’s actual FQDN regardless of the host’s domain, select the Append These DNS Suffixes option and list each domain in the order you want them tested.