Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 286
  • Last Modified:

DNS Issues

I have an old 2000 Server acting as the DC.  I have two additional servers 2000 and 2003 also running active directory.  I have introduced a 2008 server which will be replacing both the 2000 servers.  I have done all the adprep work, ran dcpromo created the DNS role as directed when running the dcpromo, (did not add a forwarding zone because not quite clear what that does) and did all the role transfers.  The 2000 server has DNS running and the 2008 has DNS running.

All the workstations have static ip's and they where first pointing to the old server now they are directed to the new server. I have no login issues or login script issues and everyone can access data on the new server without issues.

Once I finished making the changes to the static DNS on the workstations, I turned off the DNS service on the old server and have been running fine for the last week.  Today I introduced a new computer I assigned it a static IP with the DNS pointing to the new server and when I tried to join the domain, I keep getting messages that the DNS cannot resolve the domain name.  I can ping both the ip address and the server name without problems.  When I started the old DNS service and changed the DNS ip to reflect the old DC server it popped in just fine.

I am confused.  Any suggestions.

Thanks
0
imajava
Asked:
imajava
  • 2
  • 2
2 Solutions
 
Adam BrownSr Solutions ArchitectCommented:
What FSMO roles do you have assigned to the Windows 2000 server?
0
 
imajavaAuthor Commented:
I transferred the 4 roles from the 2000 server using the ntdcutil.exe.  Should I use the snap-in tools and check to see if the roles where transferred?
0
 
Adam BrownSr Solutions ArchitectCommented:
Yes. Make sure that it has none of the 5. You'll also want to check Active Directory Sites and Services to make sure that the Windows 2000 server is not listed as the primary server for your site.
0
 
imajavaAuthor Commented:
The 2000 server was the very first so I am assuming all roles where present on the server
0
 
vagedis23Commented:
All FSMO´s were still on your old DC, The primary- ad integrated DNS Forward zone is required for active directory. I recommend using DHCP for your client PCs, so they can securely and dynamically register in the DNS zone.
Because the rid-master role was still on your old DC, a new computer account could not be created, so it could not join the domain.
You could remove Active directory from the old dc by running dcpromo.exe on it, all FSMO´s will automatically be moved to the new DC in your network.
 
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now