General discussion

Locked

Windows 2000 AD and exchange 2000

By mdelacruz ·
I Planning to upgrade our NT domain to WIN2000 Active Directory and upgrade exchange 5.5 to exchange 2000.

Our current NT domain servers and NT client had FQDN of *.us.ipin.com and our email address has an email domain of @ipin.com

Question.
Do I have change our DNS FQDN to ipin.com so both Windows 2000 active directory and exchange 2000 email domain would work?

If I stay with our current setup and decided to upgrade to Windows 2000 AD and exchange 2000. What problem would arise to this scenario.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Windows 2000 AD and exchange 2000

by jmulvey In reply to Windows 2000 AD and excha ...

Hi there,

You do not necessarily have to have your Active Directory domain name (the domain into which your users login) be the same as your email domain name.

You probably WILL have to have the actual Exchange 2000 server change its internal FQDN... however Exchange 2000 will resolve and deliver mail for other domain names.

A common hypothetical example of this would be a company that is very interested in security of their Windows 2000 Domain. They might choose a Windows 2000 Domain Name such as "company.local" to avoid anyone resolving and contacting their DCs via Internet DNS. So while they would still send/receive email as "company.com", the Windows 2000 DNS would actually be "company.local".

Hope this helps,
- Jim

Collapse -

Windows 2000 AD and exchange 2000

by mdelacruz In reply to Windows 2000 AD and excha ...

The question was auto-closed by TechRepublic

Collapse -

Windows 2000 AD and exchange 2000

by tony.colgrove In reply to Windows 2000 AD and excha ...

Email addresses in Exchange 2000 do not have to have the same FQDN as your servers. You can use *.us.ipin.com in your internal namespace and still use @ipin.com for email. Just as Exchange 5.5 uses a Site Addressing template, so does Ex2000.
Depending on your overall environment, you might want to first implement a dedicated root domain of ipin.com, and continue to upgrade your NT domain into a child domain for an added piece of security.
Read the following white paper for more info:
http://www.ins.com/knowledge/whitepapers/win2kad.asp

Collapse -

Windows 2000 AD and exchange 2000

by mdelacruz In reply to Windows 2000 AD and excha ...

The question was auto-closed by TechRepublic

Collapse -

Windows 2000 AD and exchange 2000

by mdelacruz In reply to Windows 2000 AD and excha ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums