Can I use nested DNS wildcard records
up vote
3
down vote
favorite
I would like to have multiple dns entries with wildcards such that one entry is nested as subdomain of another
CNAME *.example.com -> webserver.example.com
CNAME *.api.example.com -> apiserver.example.com
The intention being that I can use customer.example.com
to access the webserver and customer.api.example.com
to access the api server.
Since customer.api.example.com
is a valid match for both of the wildcard entries i'm not sure how this will get resolved.
I have tested this on AWS route53 as the DNS provider and it seems to work as expected.customer.api.example.com
resolved to the api server. But i'm not sure if this is guaranteed by the DNS spec or was just chance it picked the correct server.
Is this behaviour something I can rely on to be consistent?
domain-name-system wildcard-subdomain
New contributor
add a comment |
up vote
3
down vote
favorite
I would like to have multiple dns entries with wildcards such that one entry is nested as subdomain of another
CNAME *.example.com -> webserver.example.com
CNAME *.api.example.com -> apiserver.example.com
The intention being that I can use customer.example.com
to access the webserver and customer.api.example.com
to access the api server.
Since customer.api.example.com
is a valid match for both of the wildcard entries i'm not sure how this will get resolved.
I have tested this on AWS route53 as the DNS provider and it seems to work as expected.customer.api.example.com
resolved to the api server. But i'm not sure if this is guaranteed by the DNS spec or was just chance it picked the correct server.
Is this behaviour something I can rely on to be consistent?
domain-name-system wildcard-subdomain
New contributor
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I would like to have multiple dns entries with wildcards such that one entry is nested as subdomain of another
CNAME *.example.com -> webserver.example.com
CNAME *.api.example.com -> apiserver.example.com
The intention being that I can use customer.example.com
to access the webserver and customer.api.example.com
to access the api server.
Since customer.api.example.com
is a valid match for both of the wildcard entries i'm not sure how this will get resolved.
I have tested this on AWS route53 as the DNS provider and it seems to work as expected.customer.api.example.com
resolved to the api server. But i'm not sure if this is guaranteed by the DNS spec or was just chance it picked the correct server.
Is this behaviour something I can rely on to be consistent?
domain-name-system wildcard-subdomain
New contributor
I would like to have multiple dns entries with wildcards such that one entry is nested as subdomain of another
CNAME *.example.com -> webserver.example.com
CNAME *.api.example.com -> apiserver.example.com
The intention being that I can use customer.example.com
to access the webserver and customer.api.example.com
to access the api server.
Since customer.api.example.com
is a valid match for both of the wildcard entries i'm not sure how this will get resolved.
I have tested this on AWS route53 as the DNS provider and it seems to work as expected.customer.api.example.com
resolved to the api server. But i'm not sure if this is guaranteed by the DNS spec or was just chance it picked the correct server.
Is this behaviour something I can rely on to be consistent?
domain-name-system wildcard-subdomain
domain-name-system wildcard-subdomain
New contributor
New contributor
New contributor
asked Nov 29 at 11:36
Dave Turvey
1183
1183
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
This approach is ok, DNS server use the most specific match which is *.api.example.com
for customer.api.example.com
The behavior should be consistent because is defined in RFC 1034
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
This approach is ok, DNS server use the most specific match which is *.api.example.com
for customer.api.example.com
The behavior should be consistent because is defined in RFC 1034
add a comment |
up vote
5
down vote
accepted
This approach is ok, DNS server use the most specific match which is *.api.example.com
for customer.api.example.com
The behavior should be consistent because is defined in RFC 1034
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
This approach is ok, DNS server use the most specific match which is *.api.example.com
for customer.api.example.com
The behavior should be consistent because is defined in RFC 1034
This approach is ok, DNS server use the most specific match which is *.api.example.com
for customer.api.example.com
The behavior should be consistent because is defined in RFC 1034
answered Nov 29 at 11:47
Quantim
940513
940513
add a comment |
add a comment |
Dave Turvey is a new contributor. Be nice, and check out our Code of Conduct.
Dave Turvey is a new contributor. Be nice, and check out our Code of Conduct.
Dave Turvey is a new contributor. Be nice, and check out our Code of Conduct.
Dave Turvey 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.
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%2f942124%2fcan-i-use-nested-dns-wildcard-records%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