Re: Internal & ext'l domain on one exch server?
From: Phil S. (nospam-m-phil-NoSpam_at_123.net)
Date: 05/17/04
- Next message: Larry Haff: "ADC Connection Agreements in AD Interim Mode"
- Previous message: Tirumal Kumar [MSFT]: "RE: dsproxy.dll"
- In reply to: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Next in thread: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Reply: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 17 May 2004 17:27:37 -0400
Paul:
Please see the reply post by Massud to an original post from macfarlt. Lots
of good info.
However, to answer your question: You must do a WHOIS and find out where
your ISP registered you domain. Do not confuse Domain Registration with
DNS. Two different concepts.
You must know with what agency your domain name is registered with, and who
controls the registration, and what the account user name and password is to
modify the registration. It is a common practice for an ISP to act as an
agent and register your domain for you. They may give their name as
contacts in the registration because are still acting as an agent on behalf
of your company. Which Internet Registration agency the actual registration
is with is not important. In the US there could be 50 or 100. The one I
use is physically located in India; at least the people on the other end of
the phone are located in India.
However, if your ISP is going out of business, then they can no longer act
as your agent. Time for senior management and or lawyers to get involved to
insure they transfer registration users, and passwords, of the domain to
your business. This is important and critical for any company in today's
business climate for the senior executives to be aware of who controls the
domain name of their company. And when the registration expires, how much
is the renewal. This, in my opinion, should be included in your company's
business plan. Email address is that important. Just ask any IT person who
has gone through company merger, buy outs, or company rename about old and
new Email address, and their customers who won't change their Outlook
address book.
The registration of your domain includes your name server's IP and FQDN, and
the backup NS IP and FQDN. By changing that NS IP address at your
registration, is how you deal with changing name servers. (during the 72
hours DNS update, yes there will be duplicate locations of where you are,
but that cannot be avoided.)
By the way, there are many internet companies that offer third party web
hosting, and allow you to manage your own NS zone edit for as little as
$20.00 USD per month. Some even less. They host your web pages, take on
all the security problems, while you host your own Exchange server behind
your own firewall. (the real inexpensive ones: when I say "allow you to
manage" that means you get a single page of instructions written in geek
speak and a phone number that isn't answered.)
Sorry about how long this message is
Phil S.
"Paul Notredame" <paul2n@hotmail.com> wrote in message
news:Cb5qc.505$u%3.144662583@hestia.telenet-ops.be...
> Thanks Phil & Lanwench for your helpful tips. I now have a solid base to
> start from. The concept of an 'official mail server' is logical but I
would
> never have thought of it.
>
> It also seems to mean that when our current ISP closes shop, our domain
name
> is up for grabs for some time; I assume I can only set up our DNS once the
> current ISP has 'released' the name, otherwise there would be 2 DNS
servers
> serving the same domain. How should I ensure the continuity of our domain
> name?
>
> Regards, Paul N
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
message
> news:%234jWXG8OEHA.904@TK2MSFTNGP12.phx.gbl...
> > In addition to the other reply -
> >
> >
> > Paul Notredame wrote:
> > > Shortly our company will move to a new ISP. Currently our external
> > > (registered) domain is hosted by the ISP. We want change that with
> > > the new ISP and do our own hosting of external mail. This would allow
> > > us to set up as many mailboxes as we need (currently some users have
> > > to share mailboxes).
> >
> > This is a good plan - see http://www.msexchange.org/tutorials/MF002.html
> > (presuming E2k, but will work for 2003 too) -
> > http://www.exchangeadmin.com/Articles/Index.cfm?ArticleID=15729 for 5.5
> > >
> > > We have an internal domain called ourcompany.lan; the external domain
> > > is ourcompany.be. We want to keep our 'private' domain name .lan for
> > > security reasons.
> >
> > That's fine; won't cause any problems.
> > >
> > > Is it possible to host these 2 domains on one exchange 2003 server?
> > > If so, how? If not, what extra hardware/software is needed?
> >
> > Nothing extra for this alone - but make sure you have a good firewall in
> > place (allow inbound port 25 forwarded to the internal IP of the
Exchange
> > server), good Exchange-aware AV software (ScanMail and Antigen are my
> > faves), and put good backup practices in place (nightly *online*
backups).
> > >
> > > Regards, Paul N
> >
> > HTH...
> >
> >
> >
>
>
- Next message: Larry Haff: "ADC Connection Agreements in AD Interim Mode"
- Previous message: Tirumal Kumar [MSFT]: "RE: dsproxy.dll"
- In reply to: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Next in thread: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Reply: Paul Notredame: "Re: Internal & ext'l domain on one exch server?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
