Question Locked

Win2003 AD DNS issues

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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....

3 replies

by bob.hunt

If so, you should use domain.local

My understanding is that .local is not routable on the internet so this will create some base security

by jacko101

Yes, it's only internal for one site. To be honest, I've found it hard to find any good information on the naming conventions, i.e the .com / .local bit.

Like I said, the forest is group.net, when I set up AD on the upgraded NT4 server, it asked for the name, so I just used the old NT4 domain name with the .com, to comply with the naming convention. This was so, we had no impact on the clients and the legacy clients can still connect using the normal netbios name.

Cheers for the info.

This discussion is closed to new replies.