Problem with PTR record registrations for non-windows based devices in Windows 2003 DNS

Posted on 2006-05-31
Last Modified: 2010-04-18
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?
Question by:wchull
    LVL 51

    Expert Comment

    Two things to check:

    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.

    Author Comment

    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.
    LVL 51

    Accepted Solution

    Either - select Always dynamically update DNS A and PTR records.


    Check - Dynamically update DNS A and PTR records for DHCP clients that do not request updates.

    You're right, there should be no functional difference, but one of the above options should correct it.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Do You Know the 4 Main Threat Actor Types?

    Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

    Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
    I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
    This video is in connection to the article "The case of a missing mobile phone (". It will help one to understand clearly the steps to track a lost android phone.
    In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…

    758 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    11 Experts available now in Live!

    Get 1:1 Help Now