Windows 7 doesnt update PTR

Hi all
I just noticed , I have a windows 7 client that never updates its PTR, evenn
after a ipconfig /registerdns.
Is there anything I can use to investigate?

regards

--
Craig

I don't believe Vista/Windows 7 will create/update a PTR lookup when they
get their IP address dynamically.

"MSNews" <> wrote in message
news:...
> Hi all
> I just noticed , I have a windows 7 client that never updates its PTR,
> evenn after a ipconfig /registerdns.
> Is there anything I can use to investigate?
>
> regards
>
> --
> Craig
>

"neo" <> wrote in message
news:...
>I don't believe Vista/Windows 7 will create/update a PTR lookup when they
>get their IP address dynamically.
>
> "MSNews" <> wrote in message
> news:...
>> Hi all
>> I just noticed , I have a windows 7 client that never updates its PTR,
>> evenn after a ipconfig /registerdns.
>> Is there anything I can use to investigate?
>>
>> regards
>>
>> --
>> Craig
>>
>


Unless it's changed, and I haven't seen any indication, and from working
with Windows 7 and Vista, they work just like 2003/XP clients. By default,
the client registers the A record, and DHCP registers the PTR.

"An example of a DHCP/DNS update interaction for Windows Server 2003-based,
Windows 2000-based, and Windows XP-based DHCP clients
Clients that are running Windows Server 2003, Windows 2000, or Windows XP
DHCP interact with DNS dynamic update protocol in the following manner:
1. The client initiates a DHCP request message (DHCPREQUEST) to the server.
The request includes option 81.
2. The server returns a DHCP acknowledgement message (DHCPACK) to the
client. The client grants an IP address lease and includes option 81. If the
DHCP server is configured with the default settings, option 81 tells the
client that the DHCP server will register the DNS PTR record and that the
client will register the DNS A record.
3. Asynchronously, the client sends a DNS update request to the DNS server
for its own forward lookup record, a host A resource record.
4. The DHCP server registers the PTR record of the client."

The above was quoted from:

How to configure DNS dynamic updates in Windows Server 2003To 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 ...
http//support.microsoft.com/kb/816592

The answer to make sure everything get registered, whether a client can or
cannot (Mac and Linux, etc), is to force DHCP to register everything (DHCP
properties). In order for it to update IP addresses for a client, configure
DHCP to own the record either by setting credentials (preferred), or if DHCP
is on a DC, add the DC to the DnsProxyUpdate group. Read more about in my
blog, link below.

Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/arc...ws-server.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Not what I am seeing when using DNS on Windows 2003 SP2 (allowing unsecured
updates) standalone and Windows XP/Vista/2003/7/2008 clients.

"Ace Fekay [MCT]" <> wrote in message
news:%...
> "neo" <> wrote in message
> news:...
>>I don't believe Vista/Windows 7 will create/update a PTR lookup when they
>>get their IP address dynamically.
>>
>> "MSNews" <> wrote in message
>> news:...
>>> Hi all
>>> I just noticed , I have a windows 7 client that never updates its PTR,
>>> evenn after a ipconfig /registerdns.
>>> Is there anything I can use to investigate?
>>>
>>> regards
>>>
>>> --
>>> Craig
>>>
>>
>
>
> Unless it's changed, and I haven't seen any indication, and from working
> with Windows 7 and Vista, they work just like 2003/XP clients. By default,
> the client registers the A record, and DHCP registers the PTR.
>
> "An example of a DHCP/DNS update interaction for Windows Server
> 2003-based, Windows 2000-based, and Windows XP-based DHCP clients
> Clients that are running Windows Server 2003, Windows 2000, or Windows XP
> DHCP interact with DNS dynamic update protocol in the following manner:
> 1. The client initiates a DHCP request message (DHCPREQUEST) to the
> server. The request includes option 81.
> 2. The server returns a DHCP acknowledgement message (DHCPACK) to the
> client. The client grants an IP address lease and includes option 81. If
> the DHCP server is configured with the default settings, option 81 tells
> the client that the DHCP server will register the DNS PTR record and that
> the client will register the DNS A record.
> 3. Asynchronously, the client sends a DNS update request to the DNS server
> for its own forward lookup record, a host A resource record.
> 4. The DHCP server registers the PTR record of the client."
>
> The above was quoted from:
>
> How to configure DNS dynamic updates in Windows Server 2003To 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 ...
> http//support.microsoft.com/kb/816592
>
> The answer to make sure everything get registered, whether a client can or
> cannot (Mac and Linux, etc), is to force DHCP to register everything (DHCP
> properties). In order for it to update IP addresses for a client,
> configure DHCP to own the record either by setting credentials
> (preferred), or if DHCP is on a DC, add the DC to the DnsProxyUpdate
> group. Read more about in my blog, link below.
>
> Configuring the Windows Time Service for Windows Server
> http://msmvps.com/blogs/acefekay/arc...ws-server.aspx
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>
>

"neo" <> wrote in message
news:%...
> Not what I am seeing when using DNS on Windows 2003 SP2 (allowing
> unsecured updates) standalone and Windows XP/Vista/2003/7/2008 clients.

What are you seeing? Are you saying updates are not working?

Ace

Hi.
All I can add is that my situation tells me windows 7 does not update the
PTR record for some reason. Could be somethin in our setup. I even try
ipconfig /registerdns and no go.


"Ace Fekay [MCT]" <> wrote in message
news:espMr$...
> "neo" <> wrote in message
> news:%...
>> Not what I am seeing when using DNS on Windows 2003 SP2 (allowing
>> unsecured updates) standalone and Windows XP/Vista/2003/7/2008 clients.
>
> What are you seeing? Are you saying updates are not working?
>
> Ace
>
>
>

"MSNews" <> wrote in message
news:%...
> Hi.
> All I can add is that my situation tells me windows 7 does not update the
> PTR record for some reason. Could be somethin in our setup. I even try
> ipconfig /registerdns and no go.
>
>


As Jonathan implied, it is difficult to assist with the limited info you are
providing.

Please provide an *unedited* ipconfig /all from one of your DCs, as well as
from a good Windows 7 workstation, and from the workstation in question.

Also provide the name of the reverse zone in arpa format (such as if the
subnet is 192.168.10.0, it should look like "10.168.192.in-addr.arpa").

Please let us know how many domains are in the forest, as well as what the
replication scope of the reverse zone is set to, if AD integrated, as well
as if the DNS address that is in the Windows 7 workstation's IP config has
the reverse zone on it, or has a reference to it (stub, secondary, etc).

This info should give us something to work on.

btw - Did you get a chance to read the articles I posted? They are extremely
informative on how this whole thing works.

Ace

I'm saying that a workgroup or domain joined Windows 7 client will only
create their A record if you point them at a workgroup setup Windows 2003 R2
server that accepts unsecured updates. If I take that very same hardware
Windows 7 was installed on and go back to Windows XP, XP creates the PTR
record w/out issue.

Don't get me wrong in thinking it is a bug, it is just a slight difference
between XP/2003 and Win7/2008R2 era. Never really cared if dynamic devices
register their PTR, but I do when it comes to static devices like servers
and it comes as a bit of shock if your site leans towards DHCP reservations.

"Ace Fekay [MCT]" <> wrote in message
news:espMr$...
> "neo" <> wrote in message
> news:%...
>> Not what I am seeing when using DNS on Windows 2003 SP2 (allowing
>> unsecured updates) standalone and Windows XP/Vista/2003/7/2008 clients.
>
> What are you seeing? Are you saying updates are not working?
>
> Ace
>
>
>

In message <> "MSNews" <>
was claimed to have wrote:

>I just noticed , I have a windows 7 client that never updates its PTR, evenn
>after a ipconfig /registerdns.
>Is there anything I can use to investigate?

Try enabling "use this connection's DNS suffix in DNS registration" and
see if this helps?

"neo" <> wrote in message
news:%...
> I'm saying that a workgroup or domain joined Windows 7 client will only
> create their A record if you point them at a workgroup setup Windows 2003
> R2 server that accepts unsecured updates.

Just to understand what you're saying, DHCP is on a stand alone machine (not
joined to a domain nor is it a DC). Correct?

> If I take that very same hardware Windows 7 was installed on and go back
> to Windows XP, XP creates the PTR record w/out issue.

Are the Windows 7 machines in a domain or stand alones?
Have you checked the NIC settings to ensure it's configured to register?

> Don't get me wrong in thinking it is a bug, it is just a slight difference
> between XP/2003 and Win7/2008R2 era. Never really cared if dynamic
> devices register their PTR, but I do when it comes to static devices like
> servers and it comes as a bit of shock if your site leans towards DHCP
> reservations.

I don't know if it's a bug or not, because I have not seen this in my two
customer's site with an R2 DC as the DHCP server and two Win7 machines among
Vista and XP machines. Then again I have DHCP configured wtih credentials
(so it can update current records), forcing it to update all and any type of
OS, as well as scavenging. Runs like a Swiss watch.

Ace


..