Re: A/D Dynamic DNS Update Problems

When I say DHCP clients, I don not refer to Static ip clients. By default XP clients request IPs to an available DHCP server, and the DHCP server takes care of the rest.

Ok, if the machine was a static IP machine then DHCP is out of question. Make sure that the servers in question are the owners of the record. When a DNS record is created by a new client, the NoRefresh interval is in effect. When the client dynamically updates its DNS information in this situation, the client's DNS time stamp is not updated until the Refresh interval takes effect. This behavior prevents the replication of lots of DNS objects in the Active Directory directory service. During the Refresh interval, the client's DNS time stamp is updated. During the Scavenging interval, old DNS resource records are automatically deleted.

If you delete the record and run from cmd ipconfig /registerdns, what happens?

Additionally check:
http://support.microsoft.com/kb/932464



--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <Trevor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:9CF8DA86-96A4-4EA0-9A6A-259C0538F5BC@xxxxxxxxxxxxxxxx
My understanding was that the DHCP server only registers those records if the
client requests it - and that by default XP clients don't request the DHCP
server to do that. Am I incorrect in that assumption?

Also, the initial machine I was troubleshooting was a Windows 2003 server
that has a statically assigned IP address, so the DHCP server would be out of
the picture.

As far as the client PCs that aren't updating their timestamps, it doesn't
appear that the DHCP server is owner of any of the records I've checked, so I
don't think that an account was specified for DNS updates.

"Jorge Silva" wrote:

Hi
Generally DNS records for clients are registered by the DHCP server that
uses a dedicated account to register those DNS records on behalf of the
clients, that account becomes the owner of those records. One common problem
is when the dedicated account used by DHCP server expires the pw or it's
removed and invalidated, is this your case?

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Trevor" <Trevor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F9291927-23B6-4291-B8CE-A705FBDBA5BB@xxxxxxxxxxxxxxxx
> Environment:
> Server 2003 SP2 DCs
> 2003 Functional Domain/Forest Level
> Server 2003 Member Servers
>
> Issue:
> I am investigating why dynamic DNS updates aren't working correctly on > our
> internal network so we can enable DNS scavenging. Scavenging IS NOT
> currently enabled, so my understanding is that the timestamp attribute
> should
> be updated whenever the ipconfig /registerdns command is run. However,
> the
> timestamp attribute is not updating - in fact, some are showing the > last
> update as > 2 years ago. In looking at the ACL for the DNS a record, > the
> host server is not on the ACL for the A record - which seems incorrect.
>
> In my personal test domain, I can see that all the clients A records > have
> the client itself in the security ACL. My question is, why aren't our
> production ACLs correct? Even by manually adding the correct ACL entry
> and
> granting FULL ACCESS rights, the timestamp attribute doesn't update.
>
> Suggestions and ideas welcome!


.

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)
Loading