You also forget to reconfigure the DHCP scope options so the clients still point at the ISP’s DNS server instead of the new DC. The DC doesn’t register SRV records in the new DNS zone and the clients wouldn’t be able to find them, even if it did. Read the rest of the column for suggestions about resolving Internet names. It accepts the flat name from the user then appends a suffix to form a FQDN it can send to a DNS server.
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.
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.
This warning message will contain the name of the zone attempted transfered, the IP address of the primary DNS server, and a description of the problem encountered.
For example: *** Warning: Failed to Zone Transfer from 22.214.171.124 (problem description) First make sure that the zone name is spelled correctly and matches the name used on the primary server, and make sure that the IP address is the correct address of your primary DNS server.
On the secondary server, check the log file or Windows Event log for any warning messages with a text starting with ”Failed to Zone Transfer...”.