Changing DNS and AD domain name

[Hal]

I have inherited a network that has teh internal DNS
domain name of a Windows 200 network with the same name
and suffix of the external domain (ex: abc.com is the
external domain and abc.com is the internal domain for
AD). This is causing DNS resolution problems for mainly
the XP machines. When a machine requests the DNS address
for a resource, the DNS forwarders are trying to query DNS
servers on the Internet, not just the local DNS server for
AD and it is taking a long time to login. Additionally
when users request resources like printers they frequently
lose connectivity to them adn have to reboot to gain
access to local resources. My question is how can I easily
remane the domain from abc.com to abc.loc (or any other
name I want) without having o touch every machine and lose
or haev to copy the local w/s config to the new profile?
Or is there and easier way to fix the DNS resolution
problems? In the past when I have changed the domain bname
in AD it has caused havoc with services and apps (like
Exchange) and I have had to reconfigure everything from
scratch. Thanks for your help.

 

[Cary Shultz [MVP]]

-----Original Message-----
I have inherited a network that has teh internal DNS
domain name of a Windows 200 network with the same name
and suffix of the external domain (ex: abc.com is the
external domain and abc.com is the internal domain for
AD). This is causing DNS resolution problems for mainly
the XP machines. When a machine requests the DNS address
for a resource, the DNS forwarders are trying to query DNS
servers on the Internet, not just the local DNS server for
AD and it is taking a long time to login. Additionally
when users request resources like printers they frequently
lose connectivity to them adn have to reboot to gain
access to local resources. My question is how can I easily
remane the domain from abc.com to abc.loc (or any other
name I want) without having o touch every machine and lose
or haev to copy the local w/s config to the new profile?
Or is there and easier way to fix the DNS resolution
problems? In the past when I have changed the domain bname
in AD it has caused havoc with services and apps (like
Exchange) and I have had to reconfigure everything from
scratch. Thanks for your help.
.

Hal,

Hold on to your boots! There is no need to change
anything OTHER THAN the DHCP Options. Your internal
WIN2000 / WINXP clients need to have your INTERNAL DNS
information only. I will bet you a dollar that they have
at least one of the IP Addresses of your ISP's DNS
Servers! This information should be found only in the
FORWARDERS tab in the FLZ of your INTERNAL DNS Server(s).

So, option 006 ( I believe ) should have only 192.168.1.30
and 192.168.10.31 ( or whatever the IP Addresses of your
INTERNAL DNS Server(s) is/are ).

Please let me know if this is not the case ( I need your
address to send you that one US Dollar! ).

HTH,

Cary