Pointing domain to AWS Classic ELB DNS Name without using Amazon route 53Elastic Load Balancing using a chain of domains/hostsHow to config Amazon Route53 working without www in sub-domainUsing Route 53 with EC2 Public DNS and Virtual HostsUsing Amazon Load Balancers to route traffic to private servers outside AmazonPointing a domain to AWS Route 53Amazon Web Services, mod_remoteip behind VPC hosted ELB occasionally sending IPv6 addressesHow to use external DNS in conjunction with an AWS Elastic Load Balancer?Is it safe to have a DNS record pointing to an unused AWS ELB instance?HOSTALIASES with Fully qualified domain namesHow to get subdomain in Route 53 to resolve to Internet-facing Elastic Load Balancer?
Am I being scammed by a sugar daddy?
Generate parentheses solution
Is all-caps blackletter no longer taboo?
ISP is not hashing the password I log in with online. Should I take any action?
Why is my Taiyaki (Cake that looks like a fish) too hard and dry?
How can I find out about the game world without meta-influencing it?
Do Veracrypt encrypted volumes have any kind of brute force protection?
Tiffeneau–Demjanov rearrangement products
Approach sick days in feedback meeting
A life of PhD: is it feasible?
Am I allowed to determine tenets of my contract as a warlock?
Did I need a visa in 2004 and 2006?
Is it true that "only photographers care about noise"?
Must I use my personal social media account for work?
What to do when the GM gives the party an overpowered item?
Fastest way from 8 to 7
What publication claimed that Michael Jackson died in a nuclear holocaust?
Was the Lonely Mountain, where Smaug lived, a volcano?
Why did the AvroCar fail to fly above 3 feet?
What game uses six-sided dice with symbols as well as numbers on the 5 and 6 faces?
Keeping track of theme when improvising
How to make this Scala method return the same generic as the input?
Is tuition reimbursement a good idea if you have to stay with the job
Why didn't all the iron and heavier elements find their way to the center of the accretion disc in the early solar system?
Pointing domain to AWS Classic ELB DNS Name without using Amazon route 53
Elastic Load Balancing using a chain of domains/hostsHow to config Amazon Route53 working without www in sub-domainUsing Route 53 with EC2 Public DNS and Virtual HostsUsing Amazon Load Balancers to route traffic to private servers outside AmazonPointing a domain to AWS Route 53Amazon Web Services, mod_remoteip behind VPC hosted ELB occasionally sending IPv6 addressesHow to use external DNS in conjunction with an AWS Elastic Load Balancer?Is it safe to have a DNS record pointing to an unused AWS ELB instance?HOSTALIASES with Fully qualified domain namesHow to get subdomain in Route 53 to resolve to Internet-facing Elastic Load Balancer?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a domain example.com.
I want to point this domain to my AWS internet-facing classic ELB public DNS (my-elb-123456789.us-west-2.elb.amazonaws.com) without using Amazon Route 53.
How should i configure elb DNS in my domain (example.com) DNS records as a CNAME?
Then what is my 'A' record in DNS configuration?
domain-name-system cname-record amazon-elb amazon-route53
asked Aug 22 '17 at 0:20
skgskg
11
add a comment |
I have a domain example.com.
I want to point this domain to my AWS internet-facing classic ELB public DNS (my-elb-123456789.us-west-2.elb.amazonaws.com) without using Amazon Route 53.
How should i configure elb DNS in my domain (example.com) DNS records as a CNAME?
Then what is my 'A' record in DNS configuration?
domain-name-system cname-record amazon-elb amazon-route53
asked Aug 22 '17 at 0:20
skgskg
11
add a comment |
I have a domain example.com.
I want to point this domain to my AWS internet-facing classic ELB public DNS (my-elb-123456789.us-west-2.elb.amazonaws.com) without using Amazon Route 53.
How should i configure elb DNS in my domain (example.com) DNS records as a CNAME?
Then what is my 'A' record in DNS configuration?
domain-name-system cname-record amazon-elb amazon-route53
asked Aug 22 '17 at 0:20
skgskg
11
I have a domain example.com.
I want to point this domain to my AWS internet-facing classic ELB public DNS (my-elb-123456789.us-west-2.elb.amazonaws.com) without using Amazon Route 53.
How should i configure elb DNS in my domain (example.com) DNS records as a CNAME?
Then what is my 'A' record in DNS configuration?
domain-name-system cname-record amazon-elb amazon-route53
domain-name-system cname-record amazon-elb amazon-route53
asked Aug 22 '17 at 0:20
skgskg
11
asked Aug 22 '17 at 0:20
skgskg
11
asked Aug 22 '17 at 0:20
skgskg
11
asked Aug 22 '17 at 0:20
skgskg
11
asked Aug 22 '17 at 0:20
skgskg
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can use any DNS provider to direct subdomain traffic to an AWS load balancer. Create a CNAME record that has the value set to the ELB CNAME. This has to be a subdomain with most DNS providers - the www subdomain would be most common. AWS Documentation.
Setting the domain apex to point at the ELB is more difficult. You can't use an A record as the IP of the ELB changes, and you can't put a CNAME at the domain apex as it's against the DNS specification.
Some providers let you create something similar to a CNAME at the domain apex, including Route53 and CloudFlare, in a way that meets the DNS specification.
If your provider won't let you set a CNAME at the domain apex you'll have to create an A record and some kind of redirection. Some options include:
- A t2.nano EC2 instance with Nginx returning a 301 redirect
- CloudFlare and a page rule (though if you're using CloudFlare it's better to use the solution above)
S3 bucket redirection (only works on http, not https)
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
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%2f869799%2fpointing-domain-to-aws-classic-elb-dns-name-without-using-amazon-route-53%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
You can use any DNS provider to direct subdomain traffic to an AWS load balancer. Create a CNAME record that has the value set to the ELB CNAME. This has to be a subdomain with most DNS providers - the www subdomain would be most common. AWS Documentation.
Setting the domain apex to point at the ELB is more difficult. You can't use an A record as the IP of the ELB changes, and you can't put a CNAME at the domain apex as it's against the DNS specification.
Some providers let you create something similar to a CNAME at the domain apex, including Route53 and CloudFlare, in a way that meets the DNS specification.
If your provider won't let you set a CNAME at the domain apex you'll have to create an A record and some kind of redirection. Some options include:
- A t2.nano EC2 instance with Nginx returning a 301 redirect
- CloudFlare and a page rule (though if you're using CloudFlare it's better to use the solution above)
S3 bucket redirection (only works on http, not https)
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
add a comment |
You can use any DNS provider to direct subdomain traffic to an AWS load balancer. Create a CNAME record that has the value set to the ELB CNAME. This has to be a subdomain with most DNS providers - the www subdomain would be most common. AWS Documentation.
Setting the domain apex to point at the ELB is more difficult. You can't use an A record as the IP of the ELB changes, and you can't put a CNAME at the domain apex as it's against the DNS specification.
Some providers let you create something similar to a CNAME at the domain apex, including Route53 and CloudFlare, in a way that meets the DNS specification.
If your provider won't let you set a CNAME at the domain apex you'll have to create an A record and some kind of redirection. Some options include:
- A t2.nano EC2 instance with Nginx returning a 301 redirect
- CloudFlare and a page rule (though if you're using CloudFlare it's better to use the solution above)
S3 bucket redirection (only works on http, not https)
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
add a comment |
You can use any DNS provider to direct subdomain traffic to an AWS load balancer. Create a CNAME record that has the value set to the ELB CNAME. This has to be a subdomain with most DNS providers - the www subdomain would be most common. AWS Documentation.
Setting the domain apex to point at the ELB is more difficult. You can't use an A record as the IP of the ELB changes, and you can't put a CNAME at the domain apex as it's against the DNS specification.
Some providers let you create something similar to a CNAME at the domain apex, including Route53 and CloudFlare, in a way that meets the DNS specification.
If your provider won't let you set a CNAME at the domain apex you'll have to create an A record and some kind of redirection. Some options include:
- A t2.nano EC2 instance with Nginx returning a 301 redirect
- CloudFlare and a page rule (though if you're using CloudFlare it's better to use the solution above)
S3 bucket redirection (only works on http, not https)
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
You can use any DNS provider to direct subdomain traffic to an AWS load balancer. Create a CNAME record that has the value set to the ELB CNAME. This has to be a subdomain with most DNS providers - the www subdomain would be most common. AWS Documentation.
Setting the domain apex to point at the ELB is more difficult. You can't use an A record as the IP of the ELB changes, and you can't put a CNAME at the domain apex as it's against the DNS specification.
Some providers let you create something similar to a CNAME at the domain apex, including Route53 and CloudFlare, in a way that meets the DNS specification.
If your provider won't let you set a CNAME at the domain apex you'll have to create an A record and some kind of redirection. Some options include:
- A t2.nano EC2 instance with Nginx returning a 301 redirect
- CloudFlare and a page rule (though if you're using CloudFlare it's better to use the solution above)
S3 bucket redirection (only works on http, not https)
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
edited May 29 at 1:35
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
answered Aug 22 '17 at 0:35
TimTim
18.8k41951
18.8k41951
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
add a comment |
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
1
1
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
If your DNS provider does let you put a CNAME at the Apex of a zone, then you have a DNS provider that doesn't understand how DNS works. This is an invalid configuration, always and everywhere. Cloudflare doesn't create a real CNAME record. Their "CNAME flattening" feature actually creates an A record and does a back-end lookup, similar in behavior to a Route 53 alias. Some providers call this an "ANAME" which is not a real RR type, but is similar to what Cloudflare is doing.
– Michael - sqlbot
Aug 22 '17 at 1:50
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
There are multiple instances where using a CNAME for ELB will not work. Some service require an A record and not a CNAME. The advantage of Route 53 is that it allows "alias" records that appear to be A records, but in the backend point to another AWS service. This is the case for both ADFS SSO, and E-mail servers (to avoid spam filtering).
– Appleoddity
Aug 22 '17 at 2:17
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%2f869799%2fpointing-domain-to-aws-classic-elb-dns-name-without-using-amazon-route-53%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
