Re: Exchange Help!!!!
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 4 Jun 2007 10:00:05 -0400
Candace Sparks <consultants1@xxxxxxxxxxx> wrote:
I did try and do the change on Friday evening. Qwest will be the new
ISP provider.
So you're changing both ISP's and nameservers for the domain?
Best not to have your ISP host your DNS, generally. I like to use something
that gives me complete access/control myself, and am fond of Dyndns' "Custom
DNS" service for this. Your ISP has nothing to do with your website, nor
your domain at all - they really ought to be handling only the connectivity.
The Web page designer wanted to have staging site set
up on the Qwest Servers before actually changing the name servers.
That shouldn't matter. Everyone needs to unlink the idea of the website from
this migration; it's irrelevant. You can leave the webhosting on the
existing server - when you create the new zone, create an A record / host of
www, pointing at the IP address of the existing website.
Qwest has the tools on their set to allow you to make the changes you
need to make, and I was unable to get a technician until Sunday
afternoon that actually understood about the staging site. I cannot
change the name servers until designer lets me know that web site
will work on Qwest servers. It has been a very frustrating weekend
for me.
I set up the old DSL modem, thinking that all would be well, Internet
works, can send external e-mail out, but not receive esternal e-mail
in. "Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23atDGpqpHHA.1244@xxxxxxxxxxxxxxxxxxxxxxx
Candace Sparks <consultants1@xxxxxxxxxxx> wrote:
I am getting ready to transfer domain for a client to another ISP.
Transfer what - the DNS hosting? If you're setting this up with
another provider (ISP isn't really the best name) have them
preconfigure the zone with all the settings you need (A record such
as mail.mydomain.com which points at the correct public IP, primary
(or sole) MX record pointing at that A record).
Then when you flip over to the new name servers, it's ready to go.
If you are also changing ISPs (i.e., the people who provide the
actual connection) you would best do this in two stages - set up the
new zone with the new DNS host with identical settings to the old
one (meaning, the old IP address would be specified), and then make
the changes (new ISP's IP address) after.
This is something you need to have arranged well ahead of time,
usually - and you would want to make the change on a Friday night or
something unless the old DNS host has set a low TTL (
I
set up the new router and got them on the Internet with the new IP
address, but was unable to complete the transfer, need to wait for
the Web Page designer.
What does the web designer have to do with it?
I put the old DSL modem back in place. Client can get on the
Internet, can send external e-mail, but cannot
receive external e-mail.
Did something get mess up in Exchange when I put the new DSL modem
in place (different IP address)?
You shouldn't have needed to change anything internally - what *did*
you change? Only your public IP settings would change.....and you
shouldn't have any public IPs referenced internally at all. I'm
presuming you've got a router/firewall in place and are not just
connecting your ISP's router/modem directly to a NIC on your server
(which is not recommended).
Thank you for your help in advance!
Candace Sparks
.
- References:
- Exchange Help!!!!
- From: Candace Sparks
- Re: Exchange Help!!!!
- From: Lanwench [MVP - Exchange]
- Re: Exchange Help!!!!
- From: Candace Sparks
- Exchange Help!!!!
- Prev by Date: Re: Maximum user limit with sbs2003 R2
- Next by Date: Re: Upgrade To Trend 3.6
- Previous by thread: Re: Exchange Help!!!!
- Next by thread: RE: PPTP VPN connection problems
- Index(es):
Relevant Pages
|
