Re: Rename Domain
- From: "NY Steve" <j@xxx>
- Date: Mon, 11 Dec 2006 15:58:04 -0500
you will have no problem.... think about it: abc.com exists on the public
inyetnet AND as your internal domain name. when youre home, going to
www.abc.com works fine because your ISP dns servers resolve to the public
address. when youre IN your office however, www.abc.com will try to resolve
internally because DNS in AD believes it owns the domain. the simple
solution is to create A records in DNS pointing www (and others) to the
external addresses so they dont try to resolve internally.... get it?
"blaine" <blaine@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CF6E1BCF-D22B-4824-AF86-85F86CA765DC@xxxxxxxxxxxxxxxx
Child Domains: The extra servers being istalled will be located in branch
offices acting as DC, DNS, DHCP, FS and PS. This adds some domain
security.
Correct?
I am following the Branch Office type of setup.
You don't think I would have any problems with keeping the same internal
and
external domain name?
Blaine
"Lanwench [MVP - Exchange]" wrote:
In news:16D95562-D58C-4421-83ED-FE6902C32BCD@xxxxxxxxxxxxx,
blaine <blaine@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hello;
We have 1 domain name for our internal domain and external website.
company.com. It has been brought to my attention that this may cause
problem for us in the future.
Meh. The only problem you're likely to have is that internal users who
try
to go to your publicly hosted website/whatnot at whatever.company.com
will
not be able to reach it unless you create static host entries in your AD
DNS, which is easy enough to do.
Renaming a domain with Exchange in the picture is not a pretty thing and
I
would avoid it....unless you absolutely must do so, and in this case I
don't
see the point.
We currently have 2 - 2k3 servers, 1
with exchange 2003 and the other with DC,DNS, DHCP, AD, SQL 2005, 2
IIS websites and 15 users. In the near future, (3 month from now) we
will be adding a child domain,
Why a child domain, just out of curiosity?
10 servers, and 100 users on this
domain. I beleive that if we need to change our domain name, we
should do it now before adding the child/servers/users.
new.company.com
From reading some documents, it soulds like the best and the cleanest
solution to this is the creat the new domain and transfer our current
user over to this new domain name and demote the old domain. But I
have some questions. How will this affect our current runnig
programs.
How will this affect the our current users sign-ons (Active
Directory)? I will need to visit every PC and rejoin to the new
domain. Will this curate a new user on the domain and will I need to
transfer the user data to the new domain user.
How will this affect the SQL 2005? What do I need to do to make sure
everyone still have the same access. (I was thinking we just demote
this server and attach it to the new domain or just rebuild it
(something similar upgrading from SQL 2k to 2K3))
How will this affect the exchange server? will email still work as
@company.com.
What steps can I follow to move the exchange svr to the new domain?
Any insight would be help. Thanks for your time.
Blaine
.
- References:
- Re: Rename Domain
- From: Lanwench [MVP - Exchange]
- Re: Rename Domain
- From: blaine
- Re: Rename Domain
- Prev by Date: Re: Help Please with exchange setup for non-profit cancer think tank
- Next by Date: Re: Rename Domain
- Previous by thread: Re: Rename Domain
- Next by thread: Re: Rename Domain
- Index(es):
Relevant Pages
|
