This option is used for redundancy and load balancing. Stores the new zone in Active Directory. This option provides secure updates and integrated storage. Stores a master copy of the new zone in a text file. Creates a copy of an existing zone.
This option helps balance the processing load of primary servers and provides fault tolerance. If you chose to create a standard primary zone in the previous step, the Zone Name dialog box appears. This dialog box allows you to specify the name of the zone. The zone name should be your registered domain name. Enter a name and click the Next button. The Zone File dialog box appears, as shown in Figure 9. This dialog box allows you to create a new file for the zone or to use an existing file that may have been copied from another computer.
After you make your selection, click the Next button. Specify the subnet in forward order, and the wizard will automatically reverse it to create the necessary reverse lookup zone. Windows automatically creates the SOA and NS records when you create a zone, and you can leave these as is or modify them.
To create new records, open the DNS console, expand the Forward Lookup Zones branch, right-click the zone, and choose the type of record you want to create or choose Other New Records to select from a complete list.
When you create a host record, you specify the hostname www, ftp, mail, etc. If you need to create a dotted host, first create the subdomain, then create the host in the subdomain. The zone should have a host record for server3 that points to the appropriate IP address, as well as a CNAME for www that points to the same IP address or possibly a different address if the server has multiple IP addresses bound to it.
You can leave this field blank if the mail exchanger name is the same as the parent domain name. The FQDN you specify must resolve to an existing host record in the domain, so make sure you create the A record for the mail exchanger as well as the MX record.
Finally, specify the preference number for the mail exchanger in the Mail Server Priority field. The higher the number, the lower the priority. These records are particularly useful in domains where multiple servers offer specific services, such as multiple HTTP servers in a single domain.
You can use the SRV records to move a service from one host to another with minimal reconfiguration, and also to designate certain servers as primary for a service and others as secondary. The DNS server responds to the request with a list of all servers in the domain that offer the requested service, and the client uses that list to determine which server to use. Select Service Location from the list and click Create Record. In the New Resource Record dialog box, specify the following information: Service: Select one of the predefined service types from the Service drop-down list.
Protocol: Select either tcp or udp, depending on the requirements of the service. Priority: This value, an integer between 0 and , specifies the preference order of the service in much the same way the preference number for an MX record specifies the priority of the mail exchanger. The lower the number, the higher the priority. The client attempts to connect to the server with the highest priority first.
If that fails, the client attempts to connect to servers with decreasing priority. You can specify the same priority for multiple records. Weight: This integer value between 0 and allocates a weight to the server to provide for load balancing. The weight parameter acts as a secondary priority indicator when multiple servers have the same priority number.
Hosts with a higher weight lower integer value are returned to the resolver first. Port Number: Specify the integer value of the tcp or udp port used by the service. Open the DNS console, right-click the zone, and choose Properties. Click Pause to pause a running zone or click Start to start a paused zone. Use Pause when you need to take a zone offline while making extensive changes to it.
Type: Indicates the current zone type. Click Change to change it to any of the supported types AD-integrated, standard primary, or standard secondary. You can allow unsecured updates, allow only secured updates, or deny updates. Aging: Specifies record aging and scavenging properties for the zone. The DNS service increments this number by 1 each time a zone transfer occurs. Other servers use this value to determine when a zone transfer is required.
Primary Server: This is the hostname of the primary master for the selected zone. You can change the server manually or click Browse to browse the network for the server. If you specify the name manually, be sure to include a trailing period. Responsible Person: You use this property to define the e-mail address of the person responsible for managing the zone. Enter the name as an FQDN, replacing the sign with a period. For administrator techrepublic. Refresh Interval: This value specifies how often servers that host secondary copies of the zone should check the currency of their zone data against the primary zone data.
The default is 15 minutes. Retry Interval: This value specifies the amount of time that must elapse before a server hosting a secondary copy of the zone retries a connection to the primary zone if a previous connection attempt failed.
To verify your domain controller's DNS client settings, type the following command at a command prompt to view the details of your Internet Protocol IP configuration:. Right-click My Network Places , and then click Properties. Right-click Local Area Connection , and then click Properties. Click Advanced , and then click the DNS tab. To configure the DNS information, follow these steps:. Verify that the Register this connection's addresses in DNS check box is selected.
To clear the DNS resolver cache, type the following command at a command prompt:. There should be a host record for the computer name. This host record is an "A" record in Advanced view. Configure the DNS client settings on the domain controller to point to a DNS server that is authoritative for the zone that corresponds to the domain where the computer is a member. Up-time and bandwidth determine reliability. On Windows Server and Windows Server member servers, Microsoft recommends that you configure the DNS client settings according to these specifications:.
If you do so, you may experience issues when you try to join the Windows based or Windows Server based server to the domain, or when you try to log on to the domain from that computer. If you have servers that are not configured to be part of the domain, you can still configure them to use Active Directory-integrated DNS servers as their primary and secondary DNS servers.
If you have non-member servers in your environment that use Active Directory-integrated DNS, they do not dynamically register their DNS records to a zone that is configured to accept only secure updates. For more information about DNS client-side name resolution, click the following article number to view the article in the Microsoft Knowledge Base:.
Windows Servers More Need more help? Expand your skills. Get new features first. Was this information helpful?
0コメント