Then do the same thing again with the other name and address; put "ns2" (without ending in a period) or "ns2." (with a period at the end) in "Name", and "y.y.y.y" in "Address" and click the button "Add an A Record".If you have not yet created or migrated in a c Panel account for the domain the nameservers are named for, it is strongly recommended to wait until such a c Panel account exists, so that the dns zone you would be making changes to does not get overwritten in the migration, possibly removing the new A records.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.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).
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.Don’t forget to include the FQDN of the local domain as the first option on the list.There may also be other situations where you may want to create new nameservers, but these are the most common reasons.If you prefer to do this part yourself, the instructions are below: and then go to Home » Domains » Simple Zone Editor.Then, you would use the "Add an A Record" section twice.