Register this connections's addresses in DNS - not working!

[Claude Lachapelle]

Since we activated scavenging we discovered that we have a lot of servers
running Server 2003 are not refreshing their host A record, because they were
deleted (considered as stale records)!!!

Even if we run ipconfig /registerdns, their records are not updated -- only
manually deleting them, and running ipconfig /registerdns again allow the
server to recreate the record.

DNS suffixes correct (even if we specify one), DNS zone accept secure and
non-secure update, and no error in event logs.

What's wrong?

Thanks.

Claude Lachapelle
La Coop fédérée, Systems Administrator

[Ace Fekay [MVP-DS, MCT]]

Post by Claude Lachapelle
Since we activated scavenging we discovered that we have a lot of servers
running Server 2003 are not refreshing their host A record, because they were
deleted (considered as stale records)!!!
Even if we run ipconfig /registerdns, their records are not updated -- only
manually deleting them, and running ipconfig /registerdns again allow the
server to recreate the record.
DNS suffixes correct (even if we specify one), DNS zone accept secure and
non-secure update, and no error in event logs.
What's wrong?
Thanks.
Claude Lachapelle
La Coop fédérée, Systems Administrator

It appears the servers may not have owned their own record, which is a prerequisite to updating their own records. If they were manually created, or set by a DHCP reservation, that would explain what happened.

You may want to also set credentials in DHCP so the DHCP server owns the records it updates in order to update new IP leases to the same machine. Take a look at my blog on this to better explain and assist you in this task.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the DnsProxyUpdate Group (How to remove duplicate DNS host records)
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

[Claude Lachapelle]

Finally we find out that was Mcafee which was preventing updates from dns.exe
to lsass.exe, we deactivated the "Access protection" feature and now it is
working properly:

04/03/2010 9:58:14 PM Blocked by port blocking rule
C:\WINDOWS\System32\dns.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6667
05/03/2010 4:05:42 PM Blocked by port blocking rule
C:\WINDOWS\system32\lsass.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6668
08/03/2010 6:41:16 PM Blocked by port blocking rule
C:\WINDOWS\System32\dns.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6666
09/03/2010 1:08:15 PM Blocked by port blocking rule Anti-virus Standard
Protection:Prevent mass mailing worms from sending mail 192.168.0.89:25

Post by Ace Fekay [MVP-DS, MCT]

Post by Claude Lachapelle
Since we activated scavenging we discovered that we have a lot of servers
running Server 2003 are not refreshing their host A record, because they were
deleted (considered as stale records)!!!
Even if we run ipconfig /registerdns, their records are not updated -- only
manually deleting them, and running ipconfig /registerdns again allow the
server to recreate the record.
DNS suffixes correct (even if we specify one), DNS zone accept secure and
non-secure update, and no error in event logs.
What's wrong?
Thanks.
Claude Lachapelle
La Coop fédérée, Systems Administrator

It appears the servers may not have owned their own record, which is a prerequisite to updating their own records. If they were manually created, or set by a DHCP reservation, that would explain what happened.
You may want to also set credentials in DHCP so the DHCP server owns the records it updates in order to update new IP leases to the same machine. Take a look at my blog on this to better explain and assist you in this task.
DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the DnsProxyUpdate Group (How to remove duplicate DNS host records)
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group..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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
.

[Ace Fekay [MVP-DS, MCT]]

Post by Claude Lachapelle
Finally we find out that was Mcafee which was preventing updates from dns.exe
to lsass.exe, we deactivated the "Access protection" feature and now it is
04/03/2010 9:58:14 PM Blocked by port blocking rule
C:\WINDOWS\System32\dns.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6667
05/03/2010 4:05:42 PM Blocked by port blocking rule
C:\WINDOWS\system32\lsass.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6668
08/03/2010 6:41:16 PM Blocked by port blocking rule
C:\WINDOWS\System32\dns.exe Anti-virus Standard Protection:Prevent IRC
communication 192.168.0.89:6666
09/03/2010 1:08:15 PM Blocked by port blocking rule Anti-virus Standard
Protection:Prevent mass mailing worms from sending mail 192.168.0.89:25

You must have set McAfee for "Maximum Protection." I usually set it for Standard Protection and then tweak the settings due to what you've experienced.

Glad to hear you figured it out.

Ace