PTR Regististration issue for Non-Windows Devices in W2K3 DNS

[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.

 

[Ace Fekay [MVP]]

In W C Hull <[email protected]> stated,
which I commented on below:

<snipped>

This was multiposted (and not cross-posted, which would have been beneficial
for all involved) between this newsgroup and the
microsoft.public.windows.server.dns group.

For anyone interested, please check the thread (with the same subject name)
in that other group for this discussion.

Thanks,

Ace

 

[W C Hull]

I understand that I posted this on two news groups but you indicate that I
should have cross posted this. Call me a newbe but have never heard of
cross posting I am unfamiliar with how to go about cross post something.
Can you enlighten me on how I could have done a better job with this?

 

[Ace Fekay [MVP]]

In

I understand that I posted this on two news groups but you indicate
that I should have cross posted this. Call me a newbe but have never
heard of cross posting I am unfamiliar with how to go about cross
post something. Can you enlighten me on how I could have done a
better job with this?

Just an FYI, I hope I didn't come across as derogatory. I was letting others
know that this thread existed in another group and would suggest they read
it prior to posting to ensure the topic/suggestions/comments weren't already
covered or mentioned.

You can use Outlook Express or any other news reader of your choice. Since
you are using Outlook (as indicated in the properties of your post), simply
click on the "Newsgroups" button that it is posting to (similar to the "To:"
when emailing multiple people) and just select the newsgroups you want to
send it to additionally. THe beauty of it is if one person responds in the
another group, the response gets sent to all groups for all to see and
respond, if they desire. Each post from any group gets sent to all at the
same time.

With a cross post, I usually state in the end of the post after my signature
that it was cross-posted and to the groups it was cross-posted to. If I set
a follow-up (means all responses only go to that group I set the follow-up
for), I would state that as well. In your case, I wouldn't set a follow-up.
Here's an example:

-----------------
Body of post

Ace

Note: X-posted to:
microsoft.public.windows.server.dns
microsoft.public.win2000.dns
F/ups set to microsoft.public.win2000.dns
----------------

More info:

Dear Emily Posthttp://www.templetons.com./brad/emily.html

Multiposting vs Crossposting:
http://www.blakjak.demon.co.uk/mul_crss.htm

Why and how to crosspost:
http://www.cs.tut.fi/~jkorpela/usenet/xpost.html

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace