• Main Menu
  • Integrating the DNS Server with DHCP and WINS


    Configuring DNS Server and DHCP Integration

    Windows 2000, Windows XP, and Windows Server 2003 clients can dynamically update their own resource records in Windows Server 2003 DNS. DHCP can also be used to configure down-level clients as DHCP clients.

    To enable the DHCP server to dynamically update clients;

    1. Click Start, Administrative Tools, and then click DHCP to open the DHCP console.

    2. Expand the DHCP server node in the console tree.

    3. Select and then right-click the DHCP scope, and then click Properties on the shortcut menu.

    4. Click the DNS tab.

    5. The DHCP updating DNS configuration settings on the DNS tab determine the manner in which DHCP client leases are integrated with the Windows Server 2003 DNS server's database.

    6. Select the Enable DNS dynamic updates according to the settings below checkbox to enable the DHCP server to dynamically update its clients.

    7. Select the Dynamically update DNS A and PTR records only if requested by DHCP clients option if the client is a Windows 2000, Windows XP or Windows Server 2003.

    8. Select the Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0) checkbox if the client is a down-level client such as a client running Windows NT 4.0.integrating the DNS server with DHCP and wins

    9. Select the Always dynamically update A and PTR records option to enable the DHCP server to always dynamically update both the A and PTR resource records in DNS.

    10. Select the Discard A and PTR records when lease is deleted checkbox if you want the A record associated with a client deleted when the DHCP server receives a DHCP release message.

    11. Click OK.

    In order for a DHCP server to register host names for DHCP clients, you have to perform the following tasks:

    • Create a user account in Active Directory that the DHCP server will use for dynamic updates.

    • Configure each DHCP server in your environment to use this specific account

    To create an Active Directory user account;

    1. Open the Active Directory Users and Computers console.

    2. In the console tree, right-click the container in which the new user account should be created, and then select New, and then User from the shortcut menu.

    3. When the New Object – User dialog box appears, enter the user's first name, initials, and last name in the provided fields. The information specified in these fields is used to populate the Full Name field. This is the user's display name.

    4. Enter the logon name for the user in the User Logon Name field, and select the domain to which the account should be associated with.

    5. The initial characters of the User Logon Name field populate the User logon name (pre-Windows 2000) field. Click Next.

    6. Proceed to set the password of the user in the Password and Confirm Password fields, and enable any applicable options available in the dialog box for the new user account.

    7. Click Next, and then click Finish.

    To configure each DHCP server use this specific account;

    1. Click Start, Administrative Tools, and then select DHCP to open the DHCP console.

    2. In the console tree, right-click the specific DHCP server, and then select Properties from the shortcut menu.

    3. When the DHCP server's Properties dialog box opens, click the Advanced tab.

    4. In the DNS dynamic updates registration credentials section of the Advanced tab, click the Credentials button.

    5. When the DNS Dynamic Update Credentials dialog box opens, specify the user name, domain and password of the user account that the DHCP server should use.

    6. Click OK.

    Configuring DNS Server and WINS Integration

    When WINS and DNS are integrated, DNS is able to query the name database of the WINS server on behalf of its clients for name resolution after the query cannot be resolved in DNS.

    The process that occurs to resolve names when DNS and WINS are integrated is illustrated below.

    1. The name resolution query is sent to the preferred DNS server.

    2. This preferred DNS server than passes the query to the authoritative DNS server for the particular zone.

    3. The authoritative DNS server sends the request for name resolution to its specified WINS lookup server.

    4. The specified WINS lookup server resolves the name into its associated IP address.

    5. The IP address is returned to the authoritative DNS server for particular zone.

    6. The authoritative DNS server returns the IP address to the preferred DNS server.

    7. The preferred DNS server returns the resolved query to the original client that sent the query for name resolution.

    To configure DNS and WINS integration;

    1. Click Start, Administrative Tools, and then click DNS to open the DNS console.

    2. In the console tree, expand the DNS server node.

    3. Expand the Forward Lookup Zones folder.

    4. Locate and right-click the zone that you want to configure, and then select Properties from the shortcut menu.

    5. Select the WINS tab.

    6. Select the Use WINS forward lookup checkbox.

    7. Enter the IP address of the WINS server and then click the Add button.

    8. If you want to add additional WINS server IP addresses, enter each individual IP address and click the Add button each time.

    9. Click the Advanced button.

    10. The options that you can configure on the Advanced dialog box are Cache time-out and Lookup time-out intervals.

    11. Enter the cache time-out TTL value in the Cache time-out field. The value you set would determine the time duration that your DNS servers can cache WINS records which originated from the WINS forward lookup server.

    12. Enter the lookup time-out TTL value in the Lookup time-out field. The value you enter would determine how long the DNS server waits for a response from a WINS forward lookup server.

    13. Click OK

    Related Articles on DNS

    Got Something To Say:

    Your email address will not be published. Required fields are marked *

    Microsoft DNS
    } 143 queries in 0.454 seconds.