AWS Load Balancer: changing A recordNginx set_real_ip_from AWS ELB load balancer addressElastic Load Balancing using a chain of domains/hostsUsing htaccess with Elastic Load Balancer and Route 53AWS Route 53 alias-record change takes too longCan a CNAME record not include www?Possible to point ALL DNS resolution to a cname?Connecting public facing application load balancer to a private load balancerPointing domain to AWS Classic ELB DNS Name without using Amazon route 53How to use external DNS in conjunction with an AWS Elastic Load Balancer?When Migrating a domain from an A record to a CNAME is Order Important
Drawing lines to nearest point
Can the sorting of a list be verified without comparing neighbors?
Why doesn't Rocket Lab use a solid stage?
Why does the Earth follow an elliptical trajectory rather than a parabolic one?
Run script for 10 times until meets the condition, but break the loop if it meets the condition during iteration
Exclude loop* snap devices from lsblk output?
How to slow yourself down (for playing nice with others)
For the erase-remove idiom, why is the second parameter necessary which points to the end of the container?
Why do Thanos's punches not kill Captain America or at least cause some mortal injuries?
What does "Ich wusste, dass aus dir mal was wird" mean?
Early arrival in Australia, early hotel check in not available
How are one-time password generators like Google Authenticator different from having two passwords?
Extracting sublists that contain similar elements
Is the schwa sound consistent?
List software from restricted, multiverse separately
Understanding integration over Orthogonal Group
How does Howard Stark know this?
How to make a language evolve quickly?
How did Thanos not realise this had happened at the end of Endgame?
Setting the major mode of a new buffer interactively
Smallest Guaranteed hash collision cycle length
Make all the squares explode
What are the implications of the new alleged key recovery attack preprint on SIMON?
Usefulness of complex chord names?
AWS Load Balancer: changing A record
Nginx set_real_ip_from AWS ELB load balancer addressElastic Load Balancing using a chain of domains/hostsUsing htaccess with Elastic Load Balancer and Route 53AWS Route 53 alias-record change takes too longCan a CNAME record not include www?Possible to point ALL DNS resolution to a cname?Connecting public facing application load balancer to a private load balancerPointing domain to AWS Classic ELB DNS Name without using Amazon route 53How to use external DNS in conjunction with an AWS Elastic Load Balancer?When Migrating a domain from an A record to a CNAME is Order Important
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have inherited a website that uses AWS for DNS and load balancing. However, the website will be migrated away to another server and won't need load balancing anymore. DNS will remain at AWS. I would like to ensure I remove and add the right DNS settings to make this happen.
Current A record in Route 53:
domain.com. ALIAS http://dualstack.site-loadbalancer-XXXXXXXXX.eu-west-1.elb.amazonaws.com.
This is the current record that I assume redirects to the load balancer. I don't see any TTL configured in Route 53 for this record but when I dig it consistently returns a 1 minute TTL. What I am planning to do is simply removing a record and adding a new A record instead:
domain.com. 111.222.333.444
I am not familiar enough with AWS to know if this would trigger any additional actions. I rather not touch the load balancer service at all; I simply want to direct traffic away to the new server.
Would this work or is there anything else I should take into account?
domain-name-system amazon-web-services amazon-route53
asked May 2 at 6:32
useruser
83
add a comment |
I have inherited a website that uses AWS for DNS and load balancing. However, the website will be migrated away to another server and won't need load balancing anymore. DNS will remain at AWS. I would like to ensure I remove and add the right DNS settings to make this happen.
Current A record in Route 53:
domain.com. ALIAS http://dualstack.site-loadbalancer-XXXXXXXXX.eu-west-1.elb.amazonaws.com.
This is the current record that I assume redirects to the load balancer. I don't see any TTL configured in Route 53 for this record but when I dig it consistently returns a 1 minute TTL. What I am planning to do is simply removing a record and adding a new A record instead:
domain.com. 111.222.333.444
I am not familiar enough with AWS to know if this would trigger any additional actions. I rather not touch the load balancer service at all; I simply want to direct traffic away to the new server.
Would this work or is there anything else I should take into account?
domain-name-system amazon-web-services amazon-route53
asked May 2 at 6:32
useruser
83
add a comment |
I have inherited a website that uses AWS for DNS and load balancing. However, the website will be migrated away to another server and won't need load balancing anymore. DNS will remain at AWS. I would like to ensure I remove and add the right DNS settings to make this happen.
Current A record in Route 53:
domain.com. ALIAS http://dualstack.site-loadbalancer-XXXXXXXXX.eu-west-1.elb.amazonaws.com.
This is the current record that I assume redirects to the load balancer. I don't see any TTL configured in Route 53 for this record but when I dig it consistently returns a 1 minute TTL. What I am planning to do is simply removing a record and adding a new A record instead:
domain.com. 111.222.333.444
I am not familiar enough with AWS to know if this would trigger any additional actions. I rather not touch the load balancer service at all; I simply want to direct traffic away to the new server.
Would this work or is there anything else I should take into account?
domain-name-system amazon-web-services amazon-route53
asked May 2 at 6:32
useruser
83
I have inherited a website that uses AWS for DNS and load balancing. However, the website will be migrated away to another server and won't need load balancing anymore. DNS will remain at AWS. I would like to ensure I remove and add the right DNS settings to make this happen.
Current A record in Route 53:
domain.com. ALIAS http://dualstack.site-loadbalancer-XXXXXXXXX.eu-west-1.elb.amazonaws.com.
This is the current record that I assume redirects to the load balancer. I don't see any TTL configured in Route 53 for this record but when I dig it consistently returns a 1 minute TTL. What I am planning to do is simply removing a record and adding a new A record instead:
domain.com. 111.222.333.444
I am not familiar enough with AWS to know if this would trigger any additional actions. I rather not touch the load balancer service at all; I simply want to direct traffic away to the new server.
Would this work or is there anything else I should take into account?
domain-name-system amazon-web-services amazon-route53
domain-name-system amazon-web-services amazon-route53
asked May 2 at 6:32
useruser
83
asked May 2 at 6:32
useruser
83
asked May 2 at 6:32
useruser
83
asked May 2 at 6:32
useruser
83
asked May 2 at 6:32
useruser
83
83
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
An Alias is an internal pointer to another record in Route 53. The value of the alias target is used to answer queries for the original record.
This is why, when you query for this record, you see IP addresses and a TTL that you didn't define. AWS load balancers always use small TTLs.
Replacing this with an A record that is not an alias should do exactly what you expect, with no side effects elsewhere in AWS, because the load balancer does not track the DNS entries that are pointing to it.
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
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
);
);
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%2f965517%2faws-load-balancer-changing-a-record%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
An Alias is an internal pointer to another record in Route 53. The value of the alias target is used to answer queries for the original record.
This is why, when you query for this record, you see IP addresses and a TTL that you didn't define. AWS load balancers always use small TTLs.
Replacing this with an A record that is not an alias should do exactly what you expect, with no side effects elsewhere in AWS, because the load balancer does not track the DNS entries that are pointing to it.
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
add a comment |
An Alias is an internal pointer to another record in Route 53. The value of the alias target is used to answer queries for the original record.
This is why, when you query for this record, you see IP addresses and a TTL that you didn't define. AWS load balancers always use small TTLs.
Replacing this with an A record that is not an alias should do exactly what you expect, with no side effects elsewhere in AWS, because the load balancer does not track the DNS entries that are pointing to it.
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
add a comment |
An Alias is an internal pointer to another record in Route 53. The value of the alias target is used to answer queries for the original record.
This is why, when you query for this record, you see IP addresses and a TTL that you didn't define. AWS load balancers always use small TTLs.
Replacing this with an A record that is not an alias should do exactly what you expect, with no side effects elsewhere in AWS, because the load balancer does not track the DNS entries that are pointing to it.
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
An Alias is an internal pointer to another record in Route 53. The value of the alias target is used to answer queries for the original record.
This is why, when you query for this record, you see IP addresses and a TTL that you didn't define. AWS load balancers always use small TTLs.
Replacing this with an A record that is not an alias should do exactly what you expect, with no side effects elsewhere in AWS, because the load balancer does not track the DNS entries that are pointing to it.
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
answered May 2 at 10:30
Michael - sqlbotMichael - sqlbot
16.5k3563
16.5k3563
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.
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%2f965517%2faws-load-balancer-changing-a-record%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
