Moving DNS hosting for Active site to Route 53 - with G Suite MX TTL of 1 weekHow can I see Time-To-Live...
Sum and average calculator
Turn off Google Chrome's Notification for "Flash Player will no longer be supported after December 2020."
When you have to wait for a short time
Does the telecom provider need physical access to the SIM card to clone it?
Moscow SVO airport, how to avoid scam taxis without pre-booking?
awk print conditions
How does the search space affect the speed of an ILP solver?
Cheap oscilloscope showing 16 MHz square wave
Break down the phrase "shitsurei shinakereba naranaindesu"
How can I store milk for long periods of time?
Using font to highlight a god's speech in dialogue
How to get frequency counts using column breaks by row?
Necessity of tenure for lifetime academic research
Can UV radiation be safe for the skin?
Am I required to correct my opponent's assumptions about my morph creatures?
Why do motor drives have multiple bus capacitors of small value capacitance instead of a single bus capacitor of large value?
How would a disabled person earn their living in a medieval-type town?
What is the motivation behind designing a control stick that does not move?
Existing light fixture is connected to 2 white wires, black wires are capped
Why does the U.S. military maintain their own weather satellites?
My colleague treats me like he's my boss, yet we're on the same level
Should a TA point out a professor's mistake while attending their lecture?
Divide Numbers by 0
Does using composite keys violate 2NF
Moving DNS hosting for Active site to Route 53 - with G Suite MX TTL of 1 week
How can I see Time-To-Live (TTL) for a DNS record?Will setting my DNS TTL to 86400 prevent minor DNS outages from making my site unavailable?Setting DNS TTL for an external addressName Server change & propagation works partially : Success for US and fail for IndiaMultiple, replicated DNS providers with Route 53how to add subdomain using route53 and godaddyset long ttl on host records before nameserver change?Using Route53 for web hosting but moving email to 1&1
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am following the steps outlined in this AWS guide to transfer my domain hosting from GoDaddy to AWS. Step 4 requires me to lower TTL for my existing NS Record to avoid downtime if I encounter issues. However, I see I also have MX records for my GSuite email which have a TTL of 1 week. Do I need to worry about lowering these too? From research, I believe that the MX record TTL is irrelevant because as soon as the domain has switched to AWS, requests will query there for the MX records instead of GoDaddy. Can anyone confirm/help?
amazon-web-services mx-record amazon-route53 dns-hosting ttl
New contributor
add a comment |
I am following the steps outlined in this AWS guide to transfer my domain hosting from GoDaddy to AWS. Step 4 requires me to lower TTL for my existing NS Record to avoid downtime if I encounter issues. However, I see I also have MX records for my GSuite email which have a TTL of 1 week. Do I need to worry about lowering these too? From research, I believe that the MX record TTL is irrelevant because as soon as the domain has switched to AWS, requests will query there for the MX records instead of GoDaddy. Can anyone confirm/help?
amazon-web-services mx-record amazon-route53 dns-hosting ttl
New contributor
add a comment |
I am following the steps outlined in this AWS guide to transfer my domain hosting from GoDaddy to AWS. Step 4 requires me to lower TTL for my existing NS Record to avoid downtime if I encounter issues. However, I see I also have MX records for my GSuite email which have a TTL of 1 week. Do I need to worry about lowering these too? From research, I believe that the MX record TTL is irrelevant because as soon as the domain has switched to AWS, requests will query there for the MX records instead of GoDaddy. Can anyone confirm/help?
amazon-web-services mx-record amazon-route53 dns-hosting ttl
New contributor
I am following the steps outlined in this AWS guide to transfer my domain hosting from GoDaddy to AWS. Step 4 requires me to lower TTL for my existing NS Record to avoid downtime if I encounter issues. However, I see I also have MX records for my GSuite email which have a TTL of 1 week. Do I need to worry about lowering these too? From research, I believe that the MX record TTL is irrelevant because as soon as the domain has switched to AWS, requests will query there for the MX records instead of GoDaddy. Can anyone confirm/help?
amazon-web-services mx-record amazon-route53 dns-hosting ttl
amazon-web-services mx-record amazon-route53 dns-hosting ttl
New contributor
New contributor
New contributor
asked 9 hours ago
cash22cash22
83 bronze badges
83 bronze badges
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As long as you create the MX record exactly the same in Route53 as it currently is in GoDaddy you don't need to change its TTL. Likewise with all the other records - A, CNAME, etc.
Only NS records TTL matter when switching DNS providers, create all the other records the same as they are now.
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
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',
autoActivateHeartbeat: false,
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
});
}
});
cash22 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f981438%2fmoving-dns-hosting-for-active-site-to-route-53-with-g-suite-mx-ttl-of-1-week%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
As long as you create the MX record exactly the same in Route53 as it currently is in GoDaddy you don't need to change its TTL. Likewise with all the other records - A, CNAME, etc.
Only NS records TTL matter when switching DNS providers, create all the other records the same as they are now.
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
add a comment |
As long as you create the MX record exactly the same in Route53 as it currently is in GoDaddy you don't need to change its TTL. Likewise with all the other records - A, CNAME, etc.
Only NS records TTL matter when switching DNS providers, create all the other records the same as they are now.
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
add a comment |
As long as you create the MX record exactly the same in Route53 as it currently is in GoDaddy you don't need to change its TTL. Likewise with all the other records - A, CNAME, etc.
Only NS records TTL matter when switching DNS providers, create all the other records the same as they are now.
As long as you create the MX record exactly the same in Route53 as it currently is in GoDaddy you don't need to change its TTL. Likewise with all the other records - A, CNAME, etc.
Only NS records TTL matter when switching DNS providers, create all the other records the same as they are now.
answered 8 hours ago
MLuMLu
11.7k2 gold badges27 silver badges49 bronze badges
11.7k2 gold badges27 silver badges49 bronze badges
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
add a comment |
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
I'm a newb so can't upvote, but thanks for the quick response @MLu
– cash22
8 hours ago
add a comment |
cash22 is a new contributor. Be nice, and check out our Code of Conduct.
cash22 is a new contributor. Be nice, and check out our Code of Conduct.
cash22 is a new contributor. Be nice, and check out our Code of Conduct.
cash22 is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2f981438%2fmoving-dns-hosting-for-active-site-to-route-53-with-g-suite-mx-ttl-of-1-week%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