Active Directory

By default, Windows 2000 DNS use the root hint servers on the Internet; however, you can configure forwarders to send DNS queries directly to your ISP's DNS server or other DNS servers. In most cases, when you configure forwarders, DNS performance and efficiency increases, but this configuration can also introduce a point of failure if the forwarding DNS server is experiencing problems. The root hint server can provide a level of redundancy in exchange for slightly increased DNS traffic on your Internet connection.

★ Net time mypdc /set /y

★ This synchronizes the local computer time with the server named Mypdc.

★ The /set - Time not only be queried, but synchronized with the specified server.

★ The /y switch skips the confirmation for changing the time on the local computer

Legacy operating systems continue to use NetBIOS for name resolution to find a DC; however it is recommended that you point all computers to the Windows 2000 or Windows Server 2003 DNS server for name resolution.

No. If a Windows 2000-based or Windows Server 2003-based server or workstation does not find the DC in DNS, you may experience issues joining the domain or logging on to the domain. A Windows 2000-based or Windows Server 2003-based computer's preferred DNS setting should point to the Windows 2000 or Windows Server 2003 DC running DNS. If you are using DHCP, make sure that you view scope option #15 for the correct DNS server settings for your LAN.

If you are able to query the ISP's DNS servers from behind the proxy server or firewall, Windows 2000 and Windows Server 2003 DNS server is able to query the root hint servers. UDP and TCP Port 53 should be open on the proxy server or firewall.

Check for a disjointed namespace, and then run Netdiag.exe /fix. You must install Support Tools from the Windows 2000 Server CD-ROM to run Netdiag.exe.

For each additional DC that is running DNS, the preferred DNS setting is the parent DNS server (first DC in the domain), and the alternate DNS setting is the actual IP address of network interface.

To set up DNS for a child domain, create a delegation record on the parent DNS server for the child DNS server. Create a secondary zone on the child DNS server that transfers the parent zone from the parent DNS server. Set the child DNS server to point to itself only.

The DNS service allows client computers to dynamically update their resource records in DNS and improves DNS administration. You can use DDNS in conjunction with DHCP to update resource records when a computer's IP address is changed.

1) Click Start, point to Programs, point to Administrative Tools, and then click DNS.

2) Click the appropriate zone under either Forward Lookup Zones or Reverse Lookup Zones.

3) On the Action menu, click Properties.

4) On the General tab, verify that the zone type is either Primary or Active Directory integrated.

5) If the zone type is Primary, click Yes in the Allow dynamic updates? list.

6) If the zone types is Active Directory-integrated, click either Yes or Only secure updates in the Allow dynamic updates? list, depending on whether you want DNS dynamic updates to be secure.

1) Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

2) Click the appropriate DHCP server or a scope on the appropriate DHCP server.

3) On the Action menu, click Properties.

4) Click the DNS tab.

5) To enable DNS dynamic update for DHCP clients that support it, click to select the Automatically update DHCP client information in DNS check box. This check box is selected by default.

6) To enable DNS dynamic update for DHCP clients that do not support it, click to select the Enable updates for DNS clients that do not support dynamic updates check box. This check box is selected by default.

1) Start the DNS snap-in.

2) Under DNS, expand Server1 (where Server1 is the host name of the DNS server). Expand Forward Lookup Zones.

4) Under Forward Lookup Zones, right-click the zone that you want (for example, Microsoft.com), and then click New Alias.

5) In the Alias name box, type www.

6) In the Fully qualified name for target host box, type the fully qualified host name of the DNS server on which IIS is installed. For example, type dns.microsoft.com, and then click OK.

1) Open the DNS MMC in the Secondary Name Server.

2) In the console tree, under DNS, click Host name (where Host name is the host name of the DNS server).

3) In the console tree, click Forward Lookup Zones.

4) Right-click Forward Lookup Zones, and then click New Zone.

5) When the New Zone Wizard starts, click Next to continue.

6) Click Standard secondary, and then click Next.

7) In the Name box, type the name of the zone (for example, example.com), and then click Next.

8) On the Master DNS Servers page, type the IP address of the primary name server for this zone, click Add, click Next, and then click Finish.

1) Click Start, point to Programs, point to Administrative Tools, and then click DNS.

2) In the console tree, click Host name (where Host name is the host name of the DNS server).

3) In the console tree, click Reverse Lookup Zones.

4) Right-click Reverse Lookup Zones, and then click New Zone.

5) When the New Zone Wizard starts, click Next to continue.

6) Click Standard secondary, and then click Next. In the Network ID box, type the network ID (for example, type 192.168.0), and then click Next.

7) On the Zone File page, click Next, and then click Finish.

When any records are orphaned, dynamic DNS on a Windows 2000-based server does not age these records by renaming them or by moving computers to different subnets out of their zones, unless the server is configured to perform this task. Orphans can occur if a group of computers are installed from an image, and then renamed at a later time on another subnet. The reverse look up pointers may not be deleted if the computer is disconnected from the network immediately after the installation. The automatic deletion of these records is possible by enabling the Aging and Scavenging feature on the DNS server.

1) Open the DNS manager.

2) In the left pane, under the DNS icon, right-click the server name.

3) Click Set Aging/Scavanging for all zones.

4) Click to select the Scavenge Stale Resource Records check box, and then set the interval that you want the Aging feature to use.