Always dynamically update dns a and ptr records windows 2008

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Windows Server TechCenter. Sign in.

United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Network Infrastructure Servers. Sign in to vote. Wednesday, March 30, PM. Thursday, March 31, AM.

Name protection should prevent dupes, and it will help. See how that goes, and post back, please. Monday, April 4, PM. Thank you for your response Ace. Thank you for your help with this issue. Monday, April 11, PM. Good to hear you've got it straightened out. My pleasure for the help. I see there are 2 ways of fixing this: 1. Monday, May 16, AM. Tuesday, May 17, AM. Hi, We are having the same issue and we tried added a Services account for doing Dynamic DNS update on behalf of the client.

Unfortunately, we noticed only A record being updated but not PTR. Is this a necessary and may I ask why? Asked 7 years, 3 months ago. Active 3 years, 6 months ago. Viewed 29k times. Improve this question. Roger Lipscombe Roger Lipscombe 1, 5 5 gold badges 22 22 silver badges 34 34 bronze badges. Add a comment. Active Oldest Votes. It depends on what you want to do. What's the difference between that and " DHCP always registers the name reported by the client, even if you set up a reservation.

If the client reports a name different than the one you set in the reservation, the reservation's name will be overwritten. You should properly set up DNS scavenging to delete these records, even if you have DHCP set to remove records when the lease expires it's good to have that on, but there are many cases where this just doesn't happen. If you upgrade those clients to a version supporting dynamic updates, the upgraded client cannot take ownership or update its DNS records.

To solve this problem, a built-in security group named DnsUpdateProxy is provided. If all DHCP servers are added to the DnsUpdateProxy group, the records of one server can be updated by another server if the first server fails. Also, all the objects that are created by the members of the DnsUpdateProxy group are not secured.

Therefore, the first user who is not a member of the DnsUpdateProxy group and that modifies the set of records that is associated with a DNS name becomes its owner. When legacy clients are upgraded, they can take ownership of their name records at the DNS server. If every DHCP server that registers resource records for legacy clients is a member of the DnsUpdateProxy group, many problems are eliminated. If you are using multiple DHCP servers for fault tolerance and secure dynamic updates, add each server to the DnsUpdateProxy global security group.

Also, objects that are created by the members of the DnsUpdateProxy group are not secure. Therefore, you cannot use this group effectively in an Active Directory-integrated zone that enables only secure dynamic updates unless you take additional steps to enable records that are created by members of the group to be secured. To help protect against nonsecure records or to enable members of the DnsUpdateProxy group to register records in zones that enable only secured dynamic updates, follow these steps:.

A dedicated user account is a user account whose sole purpose is to supply DHCP servers with credentials for DNS dynamic update registrations. Assume that you have created a dedicated user account and configured DHCP servers with the account credentials. The dedicated user account should be created in the forest where the primary DNS server for the zone to be updated resides.

The dedicated user account can also be located in another forest. However, the forest that the account resides in must have a forest trust established with the forest that contains the primary DNS server for the zone to be updated.

When the DHCP Server service is installed on a domain controller, you can configure the DHCP server by using the credentials of the dedicated user account to prevent the server from inheriting, and possibly misusing, the power of the domain controller.

When the DHCP Server service is installed on a domain controller, it inherits the security permissions of the domain controller. The service also has the authority to update or delete any DNS record that is registered in a secure Active Directory-integrated zone. This includes records that were securely registered by other Windows-based computers, and by domain controllers.

The dynamic update functionality that is included in Windows follows RFC By default, the name that is used in the DNS registration is a concatenation of the computer name and the primary DNS suffix. Right-click the connection that you want to configure, and then click Properties.

This default configuration causes the client to request that the client register the A resource record and the server register the PTR resource record. If the DHCP server is configured to register DNS records according to the client's request, the client registers the following records:.

To configure the client to make no requests for DNS registration, click to clear the Register this connection's address in DNS check box.

A client is multihomed if it has more than one adapter and an associated IP address. If you do not want the client to register all its IP addresses, you can configure it not to register one or more IP addresses in the network connection properties.

You can also configure the computer to register its domain name in DNS. For example, if you have a client that is connected to two different networks, you can configure the client to have a different domain name on each network.

Click to select the Enable DNS dynamic updates according to the settings below check box to enable DNS dynamic update for clients that support dynamic update. This section, method, or task contains steps that tell you how to modify the registry.