Win2003 AD DNS issues - TechRepublic
Question
May 16, 2007 at 11:21 AM
jacko101

Win2003 AD DNS issues

by jacko101 . Updated 19 years, 2 months ago

We have just upgraded the NT4 domain to an 2003 AD. It isn’t that simple though!

There was already an AD forest, which has one DC and has the DNS server in this domain.

The NT4 domain was installed as a new domain under an existing tree, however I wasn’t sure about the ‘full’ name at this point, so I called it domain.com

Users can log in and use resources, although the login takes longer than usual. However, there are replication issues and we are getting errors in the event viewer. Also the security log is getting loads of lsass.exe entries and has already filled up.

Can anyone help with firstly the naming I should use? For example, we have group.net as the forest root, so should my upgraded domain be domain.group.net, or just domain.com? (I used .com as I didn’t know any better!)

And also, how should DNS be set up? The DNS settings on the DC in the domain.com point to the DNS server in the group.net.

Also, just to complicate things, the two domains are in different subnets, does that make a difference?

I hope someone can help, as it’s driving me crazy. Sorry it’s such a long description, try typing that into google and getting any answers!

Cheers….

This discussion is locked

All Comments