Change Domain from .com to .local?

  • Thread starter Thread starter Karl Burrows
  • Start date Start date
K

Karl Burrows

I made the mistake of creating a domain in the LAN with the same name as the
Web address, so I am getting all kinds of DNS errors and clients can't
connect to the Website since it tries to resolve to the local server.

My question is can I change the domain to a .local and will that fix the DNS
issues? Second, do I have to uninstall AD since this is a PDC and then
reinstall and setup the new domain? Third, will the local clients have to
create a new login/profile to a new network or will it still resolve to the
domain name regardless of whether it is .com or .local (most are XP or
2000)? I'm trying to avoid as much brain damage as possible and it the
..local will work and I don't have to transfer everyone's info (email, etc.)
to a new profile, life would be much easier.

Thanks!!!!!!
 
Sorry, running 2000 Server with AD.


I made the mistake of creating a domain in the LAN with the same name as the
Web address, so I am getting all kinds of DNS errors and clients can't
connect to the Website since it tries to resolve to the local server.

My question is can I change the domain to a .local and will that fix the DNS
issues? Second, do I have to uninstall AD since this is a PDC and then
reinstall and setup the new domain? Third, will the local clients have to
create a new login/profile to a new network or will it still resolve to the
domain name regardless of whether it is .com or .local (most are XP or
2000)? I'm trying to avoid as much brain damage as possible and it the
..local will work and I don't have to transfer everyone's info (email, etc.)
to a new profile, life would be much easier.

Thanks!!!!!!
 
Hi Karl. That is because as far as your Active Directory clients are
concerned, your Active Directory dns zone is authoritative for your domain
and when a query for a host in that zone does not find the record, the name
resolution process stops. Use your dns Management Console to find your zone
and then select new host to add a host record for your web server. If the
name of it is www then add www and the internet ip address to the record.
That record will allow your internal network users to find that web server,
but in no way will interefere with the ability of users on the internet to
find it. --- Steve

Karl Burrows said:
I have looked at that article before, but not really sure how it applies to
a LAN. I have setup forwarders for the IP address of the website, but that
still doesn't work to resolve clients to the WAN Web address.

You might consider just adding a static record to your AD dns zone for the
web
server. --- Steve

http://www.microsoft.com/serviceproviders/whitepapers/split_dns.asp
Click to expand...
 
Back
Top