In
oldpama said:
I have a registered domain at a web hosting company that has a static
IP address. I am going to implement an office network (windows server
2003) with DSL (also with static IP)and want to utilize VPN
connections and Exchange server 2003. I will be creating a domain for
the office network and deploying active directory. I am confused
about how to maintain one primary namespace with DNS with 2 static IP
numbers. Would I use my static web hosting IP address with my network
domain but change the subnet mask 255.255.255.001 in order to
maintain the same domain name? Or would I use the static IP of the
DSL connection when setting up my network domain? If so, how can I
keep the same domain name that points to the web hosting IP? My goal
is to have one DNS namespace. I am confused about how to to merge the
two and still keep the primary domain name.
Keep in mind, internal AD domain name has nothing to do with the external
name. Nor does the internal AD domain name have anything to do with what
domains Exchange will receive/accept mail for.
Guidelines:
1. Come up with an AD DNS name that is different from the external name
(will make life easier for you). Good example is "example.local".
2. Setup DNS internally JUST FOR Active Directory. Do not use your ISP's DNS
address or your Router's address as a DNS address in your machines' IP
properties or many errors will result. Just use the MS DNS ONLY.
3. To receive mail, say for your external name, such as "example.com", in
your external DNS server, assuming it's your registrar, create an MX record
pointing to your WAN IP.
4. Port remap in your NAT/Router port 25 to the internal Exchange server's
IP.
5. In Exchange 2000 Recipient Policy, create an SMTP address called
@example.com and make sure the box is checked that states "this server is
authorative to receive mail for this domain".
6. If you want to host your external domain name on your server, it's
possible as long as the name is different than AD's name, however it is NOT
recommended due to security reasons. You're better off letting your
registrar or ISP handle DNS for you. Besides, they need two DNS servers for
the external domain, and you can only port remap one port per internal IP
thru NAT. Believe me, and it's also the consensus in the newsgroups, it is
ALOT EASIER to let your ISP or registrar handle the external namespace.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
