Move to another email server by changing the DNS entry
up vote
0
down vote
favorite
I ended up in charge of an email migration. My company wants to migrate from their own privately hosted email server to an office 365 server. This is not about saving the old emails on the old server.
What we want to do is turn off the old server and still receive emails to the old address just in case. And we might be in luck, none of the old email addresses look like the new ones, so we had this idea:
Just create duplicates of those email addresses on the new office 365 server and point the DNS server to the IP address. Can anyone estimate the feasibility of this idea at least in the abstract?
Microsoft's admin documentation seem utterly useless. They talk a lot about migrating the data. But I guess I might have overlooked something important. So if anyone can point me to the right documentation, I'd be grateful.
Thank you!
email domain-name-system office365
migrated from superuser.com Nov 28 at 13:02
This question came from our site for computer enthusiasts and power users.
add a comment |
up vote
0
down vote
favorite
I ended up in charge of an email migration. My company wants to migrate from their own privately hosted email server to an office 365 server. This is not about saving the old emails on the old server.
What we want to do is turn off the old server and still receive emails to the old address just in case. And we might be in luck, none of the old email addresses look like the new ones, so we had this idea:
Just create duplicates of those email addresses on the new office 365 server and point the DNS server to the IP address. Can anyone estimate the feasibility of this idea at least in the abstract?
Microsoft's admin documentation seem utterly useless. They talk a lot about migrating the data. But I guess I might have overlooked something important. So if anyone can point me to the right documentation, I'd be grateful.
Thank you!
email domain-name-system office365
migrated from superuser.com Nov 28 at 13:02
This question came from our site for computer enthusiasts and power users.
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I ended up in charge of an email migration. My company wants to migrate from their own privately hosted email server to an office 365 server. This is not about saving the old emails on the old server.
What we want to do is turn off the old server and still receive emails to the old address just in case. And we might be in luck, none of the old email addresses look like the new ones, so we had this idea:
Just create duplicates of those email addresses on the new office 365 server and point the DNS server to the IP address. Can anyone estimate the feasibility of this idea at least in the abstract?
Microsoft's admin documentation seem utterly useless. They talk a lot about migrating the data. But I guess I might have overlooked something important. So if anyone can point me to the right documentation, I'd be grateful.
Thank you!
email domain-name-system office365
I ended up in charge of an email migration. My company wants to migrate from their own privately hosted email server to an office 365 server. This is not about saving the old emails on the old server.
What we want to do is turn off the old server and still receive emails to the old address just in case. And we might be in luck, none of the old email addresses look like the new ones, so we had this idea:
Just create duplicates of those email addresses on the new office 365 server and point the DNS server to the IP address. Can anyone estimate the feasibility of this idea at least in the abstract?
Microsoft's admin documentation seem utterly useless. They talk a lot about migrating the data. But I guess I might have overlooked something important. So if anyone can point me to the right documentation, I'd be grateful.
Thank you!
email domain-name-system office365
email domain-name-system office365
asked Nov 28 at 12:53
SomeStranger314
31
31
migrated from superuser.com Nov 28 at 13:02
This question came from our site for computer enthusiasts and power users.
migrated from superuser.com Nov 28 at 13:02
This question came from our site for computer enthusiasts and power users.
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43
add a comment |
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You'll need to add the existing email address domain as a verified domain in Office 365 and create/modify your DNS records accordingly. Once complete, email sent to users at their "old" email address will be delivered to their mailbox in Office 365/Exchange Online.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f941981%2fmove-to-another-email-server-by-changing-the-dns-entry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You'll need to add the existing email address domain as a verified domain in Office 365 and create/modify your DNS records accordingly. Once complete, email sent to users at their "old" email address will be delivered to their mailbox in Office 365/Exchange Online.
add a comment |
up vote
2
down vote
accepted
You'll need to add the existing email address domain as a verified domain in Office 365 and create/modify your DNS records accordingly. Once complete, email sent to users at their "old" email address will be delivered to their mailbox in Office 365/Exchange Online.
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You'll need to add the existing email address domain as a verified domain in Office 365 and create/modify your DNS records accordingly. Once complete, email sent to users at their "old" email address will be delivered to their mailbox in Office 365/Exchange Online.
You'll need to add the existing email address domain as a verified domain in Office 365 and create/modify your DNS records accordingly. Once complete, email sent to users at their "old" email address will be delivered to their mailbox in Office 365/Exchange Online.
answered Nov 28 at 13:44
joeqwerty
95.1k462148
95.1k462148
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f941981%2fmove-to-another-email-server-by-changing-the-dns-entry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If the top-level domains (example.com and example.co.uk, for example) are different then this is trivial, you simply configure your MX records for the new domain to point to Office365 (once you've completed the domain verification TXT, SRV and others DNS records required) and leave the existing domain untouched so that it can continue to receive emails. You'll need to keep the email server on until you deem it suitable to decomission. Although I haven't precisely done this, I've moved to Office365 and it was easy.
– Kinnectus
Nov 28 at 12:59
There is not enough information here to present a solution. Without knowing the email address format no one can help you. Also, you don't (except in very narrowest of circumstances not applicable here) point a domain to an IP address for mail delivery - you use MX records to point to one or more mail server host names.
– davidgo
Nov 28 at 18:56
Thank you for your answers. That aligns with what I suspected and researched. Domain will be moved today, so wish me luck.
– SomeStranger314
Nov 30 at 9:43