Desktops are no longer autmatically updating DNS records

I am running windows 2003 standard servers and windows xp sp2 desktops. I
replaced one of my Domain controllers, by adding a new server making it a
domain controller, adding DNS , and DHCP, copied over the DHCP database and
activated the DHCP Removed these services from the old server, demoted the
old server and then removed it from the network. All appeared to be
working. I started having a couple users (laptop users) that stopped
resolving names on the network - could not find my exchange server etc. I
found that they correctly recieved the new DNS from the DHCP scope so they
are renewing leases correctly and with the new lease they get the change to
the new DNS server, but if I run nslookup for any internal address, it times
out trying to contact DNS. In the process of trouble shooting I noticed
that the only computers with records in DNS are the servers with fixed
addresses - Windows XP desktops are no longer autoupdating. So I took one
of the laptops and removed it from the domain, rebooted, deleted its
computer record in AD and then added it back to the domain. This computer
is now autoupdating and resolving computer names on our network.

So now I am trying to figure out what is going on, that my computers are not
correctly interacting with my DNS for my internal domains.

DNS is ad integrated. DNS server points to itself in its TCP/IP settings.
Desktop NIC TCP/IP are checked to register with DNS.


Can anyone shed any light on what I have done, or what is wrong with my
network?

Remember reading something about downlevel clients and configuring a box to
act as the authority to update their DNS records. Maybe you can look into
that.. have a temp box update the A records for all of your machines.

--Dan

"Fredrick A. Zilz" wrote:

> I am running windows 2003 standard servers and windows xp sp2 desktops. I
> replaced one of my Domain controllers, by adding a new server making it a
> domain controller, adding DNS , and DHCP, copied over the DHCP database and
> activated the DHCP Removed these services from the old server, demoted the
> old server and then removed it from the network. All appeared to be
> working. I started having a couple users (laptop users) that stopped
> resolving names on the network - could not find my exchange server etc. I
> found that they correctly recieved the new DNS from the DHCP scope so they
> are renewing leases correctly and with the new lease they get the change to
> the new DNS server, but if I run nslookup for any internal address, it times
> out trying to contact DNS. In the process of trouble shooting I noticed
> that the only computers with records in DNS are the servers with fixed
> addresses - Windows XP desktops are no longer autoupdating. So I took one
> of the laptops and removed it from the domain, rebooted, deleted its
> computer record in AD and then added it back to the domain. This computer
> is now autoupdating and resolving computer names on our network.
>
> So now I am trying to figure out what is going on, that my computers are not
> correctly interacting with my DNS for my internal domains.
>
> DNS is ad integrated. DNS server points to itself in its TCP/IP settings.
> Desktop NIC TCP/IP are checked to register with DNS.
>
>
> Can anyone shed any light on what I have done, or what is wrong with my
> network?
>
>
>