wchull
asked on
Problem with PTR record registrations for non-windows based devices in Windows 2003 DNS
Currently, we are upgrading our DNS servers from Windows 2000 to 2003 and all of our DNS servers are on domain controllers. Our production environment is still on 2000 while our test environment is on 2003.
In our test environment we have some non-windows based, DHCP enabled devices, where the foreward host records are being registered but not the reverse PTR records. We have the same devices on our production side and the DHCP scopes are setup identical but both the host and PTR records are being registered in Windows 2000 DNS. Note that windows XP devices in the test environment are registering the host and ptr records so the problem is restricted to the PTR records for non-windows based devices on a Windows 2003 DNS
I'm wondering if anyone can tell me if there is a know problem with Windows 2003 reverse PTR records for a non-windows based devices in Micorosof DNS 2003?
In our test environment we have some non-windows based, DHCP enabled devices, where the foreward host records are being registered but not the reverse PTR records. We have the same devices on our production side and the DHCP scopes are setup identical but both the host and PTR records are being registered in Windows 2000 DNS. Note that windows XP devices in the test environment are registering the host and ptr records so the problem is restricted to the PTR records for non-windows based devices on a Windows 2003 DNS
I'm wondering if anyone can tell me if there is a know problem with Windows 2003 reverse PTR records for a non-windows based devices in Micorosof DNS 2003?
ASKER
On the reverse zone Secure and Non-Secure updates is selected. On the DHCP side I have the following:
Dynamically update DNS A and PTR records only if requested by the DHCP clents, Discard A and PTR records when lease is deleted and Dynamicaly update DNA A and PTR records for DHCP clients that do not request updates. Note that the DHCP settings are exactly the same between my production DHCP scopes and my test scopes however my production DHCP and DNS are on a Windows 2000 DNS server and my test DHCP and Test DNS are on Windows 2003 server. This is why we have a concern...Everything is the same but yet we have a difference in behavior.
Dynamically update DNS A and PTR records only if requested by the DHCP clents, Discard A and PTR records when lease is deleted and Dynamicaly update DNA A and PTR records for DHCP clients that do not request updates. Note that the DHCP settings are exactly the same between my production DHCP scopes and my test scopes however my production DHCP and DNS are on a Windows 2000 DNS server and my test DHCP and Test DNS are on Windows 2003 server. This is why we have a concern...Everything is the same but yet we have a difference in behavior.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1) On the Reverse Zone make sure you select Secure and Non-Secure updates. Secure only will only allow Domain-joined devices to register.
2) On the properties of DHCP you can select the option to allow DHCP to register PTR records on behalf of the client (in this case, device).
Let us know.