2003 Server DNS problem

[porkerjoe]

Hello

I have a Windows 2003 domain running in 2003 functional mode.

I just deployed a member server to another location on a different subnet. NOTE SAME ACTIVE DIRETORY SITE but different subnet.

The server is a file and print server for that location, and also serves as the DHCP server for that location.

I configured the server at HQ, which has network address 192.168.1.0. During configuration, I let the server pick up a dynamic IP (which was 192.168.1.43). During this configuration, I Configured the DHCP server component to have a small scope on the HQ subnet. After testing, I disconnected the server from the network, deleted the test DHCP scope, set the server to have a static IP of 192.168.2.200 for its new subnet of 192.168.2.0.

When the server was hooked up to the network at the new location I was unable to connect by name. It turns out my DNS servers at HQ are showing the server's address as 192.168.1.43.

I've tried the following:

Deleting the A record from the DNS Server and then running ipconfig /registerdns on the remote server. This works - the address is updated to the correct 192.168.2.200 - but it goes back to 192.168.1.43 within a few minutes.

I also tried running ipconfig /flushdns on the DNS server, then repeating the above procedure. However, the same result happens.

Any help will be greatly appreciated.

 

[porkerjoe]

One thing I forgot to mention:

A sub-domain used to reside at the location where I just deployed the new member server. Recently the only DC for that sub-domain crashed. The sub-domain was not necessary. So, rather than restore the domain, I am just deploying a member server to the location, and will be joining the users there to the main domain. Again, this has always been a single AD site.

I have not yet deleted the sub-domain from the main domain. However, there are no DCs available for that domain anywhere, and the member server in question has definitely been joined to the main domain.

Without removing the sub-domain from AD, I just deleted the sub-domain's folder from the DNS tree. I am hoping this may be the issue.

 

[Spirit]

Somewhere the old DNS record still exists.

Do you have a spare / second DNS server?

You've not added any static mapping anywhere like in a hosts file or something?

IAin

 

[porkerjoe]

Turns out that because the server was picking up a dynamic DHCP at HQ before I switched it to static config and shipped it to the remote location; the DHCP was regularly "updating" the A record for the server with DNS.

All I had to do was go into the DHCP snap-in and delete the old lease, and the problem was solved. It would have solved itself in a few days when the lease expired.

Thanks to Spirit for the suggestions!