change internal domain suffix

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I think I need to change my internal DNS suffix. It seems that somewhere out
there someone else is using the same name and my servers and workstations are
getting confused. So, for example, I'd like to change from
workstation.123.com to workstation.123abc.com. Since I've got 2K AD and
Exchange 2K3 where would I start? I figured change the DNS servers first,
change all the 2K servers, change the DHCP options, and finally change all
the static IP workstations. Does that sound right? Would I also have to
change the name of my AD domain?
 
In
Jonathan said:
I think I need to change my internal DNS suffix. It seems that
somewhere out there someone else is using the same name and my
servers and workstations are getting confused. So, for example, I'd
like to change from workstation.123.com to workstation.123abc.com.
Since I've got 2K AD and Exchange 2K3 where would I start? I figured
change the DNS servers first, change all the 2K servers, change the
DHCP options, and finally change all the static IP workstations.
Does that sound right? Would I also have to change the name of my AD
domain?
Click to expand...

This is not an easy task. With Windows 2000 AD, it requires a complete
domain rebuild. Just changing the names ain't going to do it. Maybe a
migration using ADMT and Exmerge would be the better route for you.

If you can upgrade to Windows 2003 and Exchange 2003 (with SP1), there are
rename tools available.

Maybe you can live with your current scenario. This is actually what is
called a 'split-zone', 'split-brain' or 'split-namespace'. What sort of
issues are you having? If just the fact of trying to get to their website
and/or send email to them, you can actually manually create the necessary
records in DNS so you can communicate with them. To get to their website,
you can create a 'www' record, and give it the actual external IP address.
This way you can get to their website. If you need to send mail to them, you
can create a 'mail' record, give it the IP of their mail server, then create
an MX record, pointing to that mail record. Make sense? I mention this
assuming that you are not using your internal domain name for external
public use and inadvertenly created your AD structure using their name.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
First, I'm not trying to send mail or access their site. I want nothing to
do with this other site. I'd just like to change my internal DNS name to
something else.

And yes, I am NOT using my internal name for public use and everything was
fine until 3 weeks ago. I guess someone started using the same name just
after I setup our AD. Going to Windows 2K3 is probably not an option. So I
guess I'm stuck with the way it is or rebuild everything?
 
In
Jonathan said:
First, I'm not trying to send mail or access their site. I want
nothing to do with this other site. I'd just like to change my
internal DNS name to something else.

And yes, I am NOT using my internal name for public use and
everything was fine until 3 weeks ago. I guess someone started
using the same name just after I setup our AD. Going to Windows 2K3
is probably not an option. So I guess I'm stuck with the way it is
or rebuild everything?
Click to expand...

I guess if you have nothing to do with their site or domain name, and have
no need to access their resources, (mail or web), then I wouldn't really
worry about it. You'll be ok. If you ever need to access their resources,
just create the necessary records.

Changing the AD DNS domain name is a major, monumental task that inlcludes
more than just changing the name in DNS and on the workstations and servers.
It's actually a domain migration to a new AD domain. If you can avoid it,
and don't really need to, I believe you will be ok to keep with the current
name. However, this is a decision you will have to make.

Ace
 
Back
Top