Can't get my domain to work after update with EC2 and Route53
up vote
0
down vote
favorite
So using the amazon AWS services,
EC2 with Elastic Beanstalk I've recently tried making a SSH connection. Due to this I had to update my instance to classic auto load balancing. This changed my instance's IP. So my domain didn't direct anymore since the old ip is still in my Route53, so I went in and changed the IP to the new one, but still no results? Is there something more i need to do in order to get my Route53 working again? Don't know what else to change after I've changed my instance to auto load balancing.
amazon-ec2 ssh elastic-beanstalk amazon-route53
asked Aug 11 at 16:48
Qwern
13
add a comment |
up vote
0
down vote
favorite
So using the amazon AWS services,
EC2 with Elastic Beanstalk I've recently tried making a SSH connection. Due to this I had to update my instance to classic auto load balancing. This changed my instance's IP. So my domain didn't direct anymore since the old ip is still in my Route53, so I went in and changed the IP to the new one, but still no results? Is there something more i need to do in order to get my Route53 working again? Don't know what else to change after I've changed my instance to auto load balancing.
amazon-ec2 ssh elastic-beanstalk amazon-route53
asked Aug 11 at 16:48
Qwern
13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
So using the amazon AWS services,
EC2 with Elastic Beanstalk I've recently tried making a SSH connection. Due to this I had to update my instance to classic auto load balancing. This changed my instance's IP. So my domain didn't direct anymore since the old ip is still in my Route53, so I went in and changed the IP to the new one, but still no results? Is there something more i need to do in order to get my Route53 working again? Don't know what else to change after I've changed my instance to auto load balancing.
amazon-ec2 ssh elastic-beanstalk amazon-route53
asked Aug 11 at 16:48
Qwern
13
So using the amazon AWS services,
EC2 with Elastic Beanstalk I've recently tried making a SSH connection. Due to this I had to update my instance to classic auto load balancing. This changed my instance's IP. So my domain didn't direct anymore since the old ip is still in my Route53, so I went in and changed the IP to the new one, but still no results? Is there something more i need to do in order to get my Route53 working again? Don't know what else to change after I've changed my instance to auto load balancing.
amazon-ec2 ssh elastic-beanstalk amazon-route53
amazon-ec2 ssh elastic-beanstalk amazon-route53
asked Aug 11 at 16:48
Qwern
13
asked Aug 11 at 16:48
Qwern
13
asked Aug 11 at 16:48
Qwern
13
asked Aug 11 at 16:48
Qwern
13
asked Aug 11 at 16:48
Qwern
13
13
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
When using custom domain with Elastic Beanstalk it is not a good practice to map the domain name to your EC2 instance IP address. Instead, use the elastic beanstalk url created for the application environment. With each new version Elastic Beanstalk will provide a fresh instance with a new IP address, but it will keep the url constant.
It is even better create a A record in the Route53 (A records are implemented in AWS as a proprietary technology that integrates better the solutions) instead of CNAME. More information here (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html)
answered Aug 16 at 15:09
Gustavo Tavares
780514
add a comment |
up vote
0
down vote
As per my understanding you've changed your IP to new one but still getting the old results.
This might be due to Cached DNS which is showing the old results also it depends on TTL (Time to Live) values that specifies how long, in seconds, that you want DNS resolvers to cache the information in the record, such as the IP address for a web server.
So if you want to see the quick results set the TTL value as low as 2 min or whatever minimum is allowed.
edited Nov 15 at 9:02
piet.t
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
When using custom domain with Elastic Beanstalk it is not a good practice to map the domain name to your EC2 instance IP address. Instead, use the elastic beanstalk url created for the application environment. With each new version Elastic Beanstalk will provide a fresh instance with a new IP address, but it will keep the url constant.
It is even better create a A record in the Route53 (A records are implemented in AWS as a proprietary technology that integrates better the solutions) instead of CNAME. More information here (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html)
answered Aug 16 at 15:09
Gustavo Tavares
780514
add a comment |
up vote
0
down vote
When using custom domain with Elastic Beanstalk it is not a good practice to map the domain name to your EC2 instance IP address. Instead, use the elastic beanstalk url created for the application environment. With each new version Elastic Beanstalk will provide a fresh instance with a new IP address, but it will keep the url constant.
It is even better create a A record in the Route53 (A records are implemented in AWS as a proprietary technology that integrates better the solutions) instead of CNAME. More information here (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html)
answered Aug 16 at 15:09
Gustavo Tavares
780514
add a comment |
up vote
0
down vote
up vote
0
down vote
When using custom domain with Elastic Beanstalk it is not a good practice to map the domain name to your EC2 instance IP address. Instead, use the elastic beanstalk url created for the application environment. With each new version Elastic Beanstalk will provide a fresh instance with a new IP address, but it will keep the url constant.
It is even better create a A record in the Route53 (A records are implemented in AWS as a proprietary technology that integrates better the solutions) instead of CNAME. More information here (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html)
answered Aug 16 at 15:09
Gustavo Tavares
780514
When using custom domain with Elastic Beanstalk it is not a good practice to map the domain name to your EC2 instance IP address. Instead, use the elastic beanstalk url created for the application environment. With each new version Elastic Beanstalk will provide a fresh instance with a new IP address, but it will keep the url constant.
It is even better create a A record in the Route53 (A records are implemented in AWS as a proprietary technology that integrates better the solutions) instead of CNAME. More information here (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html)
answered Aug 16 at 15:09
Gustavo Tavares
780514
answered Aug 16 at 15:09
Gustavo Tavares
780514
answered Aug 16 at 15:09
Gustavo Tavares
780514
answered Aug 16 at 15:09
Gustavo Tavares
780514
780514
add a comment |
add a comment |
up vote
0
down vote
As per my understanding you've changed your IP to new one but still getting the old results.
This might be due to Cached DNS which is showing the old results also it depends on TTL (Time to Live) values that specifies how long, in seconds, that you want DNS resolvers to cache the information in the record, such as the IP address for a web server.
So if you want to see the quick results set the TTL value as low as 2 min or whatever minimum is allowed.
edited Nov 15 at 9:02
piet.t
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
add a comment |
up vote
0
down vote
As per my understanding you've changed your IP to new one but still getting the old results.
This might be due to Cached DNS which is showing the old results also it depends on TTL (Time to Live) values that specifies how long, in seconds, that you want DNS resolvers to cache the information in the record, such as the IP address for a web server.
So if you want to see the quick results set the TTL value as low as 2 min or whatever minimum is allowed.
edited Nov 15 at 9:02
piet.t
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
add a comment |
up vote
0
down vote
up vote
0
down vote
As per my understanding you've changed your IP to new one but still getting the old results.
This might be due to Cached DNS which is showing the old results also it depends on TTL (Time to Live) values that specifies how long, in seconds, that you want DNS resolvers to cache the information in the record, such as the IP address for a web server.
So if you want to see the quick results set the TTL value as low as 2 min or whatever minimum is allowed.
edited Nov 15 at 9:02
piet.t
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
As per my understanding you've changed your IP to new one but still getting the old results.
This might be due to Cached DNS which is showing the old results also it depends on TTL (Time to Live) values that specifies how long, in seconds, that you want DNS resolvers to cache the information in the record, such as the IP address for a web server.
So if you want to see the quick results set the TTL value as low as 2 min or whatever minimum is allowed.
edited Nov 15 at 9:02
piet.t
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
edited Nov 15 at 9:02
piet.t
9,96463245
edited Nov 15 at 9:02
piet.t
9,96463245
edited Nov 15 at 9:02
piet.t
9,96463245
9,96463245
answered Aug 11 at 17:55
rbashish
89211526
answered Aug 11 at 17:55
rbashish
89211526
answered Aug 11 at 17:55
rbashish
89211526
89211526
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f51801799%2fcant-get-my-domain-to-work-after-update-with-ec2-and-route53%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
