W
W C Hull
We are trying to identify a problem with registration of PTR records
involving some non-Windows based DHCP clients on a Windows 2003 and was
wondering if anyone can shed some light on the issue?
Currently we are upgrading our domain controllers running DHCP and DNS from
Windows 2000 to 2003 and our production environment is still Windows 2000
while our test environment is Windows 2003. In each environment we have a
large number of non-windows based devices that acquire their IP addresses
from DHCP. We have DNS in both environments set to accept secure and
non-secure updates and we have DHCP set to register Host and PTR records for
clients that cannot register themselves. Bottom line is that DHCP and DNS
are configured exactly the same in Windows 2000 as they are in Windows 2003
yet we have a difference.
On the production side (Wndows 2000) all of these non-windows based clients
have their host and PTR records registering but on the test side (Windows
2003) only the Host records are registering. We have confirmed that we
have the reverse zone setup on the test side and we have confirmed that we
can manually add PTR records to that zone. We have also confirmed that we
can change the settings in DHCP to say "ALWAYS register Host and PTR records
on behalf of the client" and yet we cannot get any PTR records to register.
Note also that in DHCP the check box for legacy (WinNT) registrations is
checked in both the production and test environments.
So, In summary we have DNS and DHCP setup with identical settings and we
have identical non-windows based
devices that will only register both the Host and PTR records in Windows
2000. Under Windows 2003 it doesn't seem to matter what settings we have
configured in DHCP, only the Host records will register in DNS.
Any insight into this matter would be greatly appreciated.
involving some non-Windows based DHCP clients on a Windows 2003 and was
wondering if anyone can shed some light on the issue?
Currently we are upgrading our domain controllers running DHCP and DNS from
Windows 2000 to 2003 and our production environment is still Windows 2000
while our test environment is Windows 2003. In each environment we have a
large number of non-windows based devices that acquire their IP addresses
from DHCP. We have DNS in both environments set to accept secure and
non-secure updates and we have DHCP set to register Host and PTR records for
clients that cannot register themselves. Bottom line is that DHCP and DNS
are configured exactly the same in Windows 2000 as they are in Windows 2003
yet we have a difference.
On the production side (Wndows 2000) all of these non-windows based clients
have their host and PTR records registering but on the test side (Windows
2003) only the Host records are registering. We have confirmed that we
have the reverse zone setup on the test side and we have confirmed that we
can manually add PTR records to that zone. We have also confirmed that we
can change the settings in DHCP to say "ALWAYS register Host and PTR records
on behalf of the client" and yet we cannot get any PTR records to register.
Note also that in DHCP the check box for legacy (WinNT) registrations is
checked in both the production and test environments.
So, In summary we have DNS and DHCP setup with identical settings and we
have identical non-windows based
devices that will only register both the Host and PTR records in Windows
2000. Under Windows 2003 it doesn't seem to matter what settings we have
configured in DHCP, only the Host records will register in DNS.
Any insight into this matter would be greatly appreciated.