How many aliases for name LINUX DNS can have
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
How many alias a HOST name can have in the LINUX DNS BIND Version 9.
For example a DNAME & CNAME records.
CNAME is terminal in the sense that when the CNAME record has been found, the job is done. Whereas, DNAME is like CNAME, but it does not alias a single name—it aliases a whole domain.
Lets Suppose i have a HOSTNAME testhost.example.com and further i want to create alias for this, Is there a restriction to that a specific number of alias a hostname can have in BIND9.
What i get to Know , `
Name Alias (CNAME)
This type of record creates an additional name for an existing Address or Reverse Address record. When a DNS client requests the IP address of a record of this type, it will get the IP of the record that the Name Alias points to instead. This kind of record can be useful if you have a single host that needs to be accessible under several different names, such as a web server doing name-based virtual hosting. Even though this could also be done by creating multiple Address records, creating just a single Address and multiple Name Aliases is more flexible as it allows easier updating if the IP address of the host ever changes. The forms for editing and creating Name Alias records contains a field labelled Real Name. This must be filled in with either the canonical name of the record that the alias points to (such as webserver.example.com.), or with a short name that is relative to the zone that the Name Alias record is in.
dns
asked Jun 6 at 17:20
user294110
11
 |Â
show 1 more comment
up vote
0
down vote
favorite
How many alias a HOST name can have in the LINUX DNS BIND Version 9.
For example a DNAME & CNAME records.
CNAME is terminal in the sense that when the CNAME record has been found, the job is done. Whereas, DNAME is like CNAME, but it does not alias a single name—it aliases a whole domain.
Lets Suppose i have a HOSTNAME testhost.example.com and further i want to create alias for this, Is there a restriction to that a specific number of alias a hostname can have in BIND9.
What i get to Know , `
Name Alias (CNAME)
This type of record creates an additional name for an existing Address or Reverse Address record. When a DNS client requests the IP address of a record of this type, it will get the IP of the record that the Name Alias points to instead. This kind of record can be useful if you have a single host that needs to be accessible under several different names, such as a web server doing name-based virtual hosting. Even though this could also be done by creating multiple Address records, creating just a single Address and multiple Name Aliases is more flexible as it allows easier updating if the IP address of the host ever changes. The forms for editing and creating Name Alias records contains a field labelled Real Name. This must be filled in with either the canonical name of the record that the alias points to (such as webserver.example.com.), or with a short name that is relative to the zone that the Name Alias record is in.
dns
asked Jun 6 at 17:20
user294110
11
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
Since any other domain anywhere in the tree could haveCNAME testhost.example.comI do not see how you could restrict the number of such records since they could be anywhere else in the tree.
– Patrick Mevzek
Jun 7 at 13:25
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How many alias a HOST name can have in the LINUX DNS BIND Version 9.
For example a DNAME & CNAME records.
CNAME is terminal in the sense that when the CNAME record has been found, the job is done. Whereas, DNAME is like CNAME, but it does not alias a single name—it aliases a whole domain.
Lets Suppose i have a HOSTNAME testhost.example.com and further i want to create alias for this, Is there a restriction to that a specific number of alias a hostname can have in BIND9.
What i get to Know , `
Name Alias (CNAME)
This type of record creates an additional name for an existing Address or Reverse Address record. When a DNS client requests the IP address of a record of this type, it will get the IP of the record that the Name Alias points to instead. This kind of record can be useful if you have a single host that needs to be accessible under several different names, such as a web server doing name-based virtual hosting. Even though this could also be done by creating multiple Address records, creating just a single Address and multiple Name Aliases is more flexible as it allows easier updating if the IP address of the host ever changes. The forms for editing and creating Name Alias records contains a field labelled Real Name. This must be filled in with either the canonical name of the record that the alias points to (such as webserver.example.com.), or with a short name that is relative to the zone that the Name Alias record is in.
dns
asked Jun 6 at 17:20
user294110
11
How many alias a HOST name can have in the LINUX DNS BIND Version 9.
For example a DNAME & CNAME records.
CNAME is terminal in the sense that when the CNAME record has been found, the job is done. Whereas, DNAME is like CNAME, but it does not alias a single name—it aliases a whole domain.
Lets Suppose i have a HOSTNAME testhost.example.com and further i want to create alias for this, Is there a restriction to that a specific number of alias a hostname can have in BIND9.
What i get to Know , `
Name Alias (CNAME)
This type of record creates an additional name for an existing Address or Reverse Address record. When a DNS client requests the IP address of a record of this type, it will get the IP of the record that the Name Alias points to instead. This kind of record can be useful if you have a single host that needs to be accessible under several different names, such as a web server doing name-based virtual hosting. Even though this could also be done by creating multiple Address records, creating just a single Address and multiple Name Aliases is more flexible as it allows easier updating if the IP address of the host ever changes. The forms for editing and creating Name Alias records contains a field labelled Real Name. This must be filled in with either the canonical name of the record that the alias points to (such as webserver.example.com.), or with a short name that is relative to the zone that the Name Alias record is in.
dns
asked Jun 6 at 17:20
user294110
11
edited Jun 6 at 17:49
asked Jun 6 at 17:20
user294110
11
asked Jun 6 at 17:20
user294110
11
asked Jun 6 at 17:20
user294110
11
11
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
Since any other domain anywhere in the tree could haveCNAME testhost.example.comI do not see how you could restrict the number of such records since they could be anywhere else in the tree.
– Patrick Mevzek
Jun 7 at 13:25
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56
 |Â
show 1 more comment
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
Since any other domain anywhere in the tree could haveCNAME testhost.example.comI do not see how you could restrict the number of such records since they could be anywhere else in the tree.
– Patrick Mevzek
Jun 7 at 13:25
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
Since any other domain anywhere in the tree could have
CNAME testhost.example.com I do not see how you could restrict the number of such records since they could be anywhere else in the tree.– Patrick Mevzek
Jun 7 at 13:25
Since any other domain anywhere in the tree could have
CNAME testhost.example.com I do not see how you could restrict the number of such records since they could be anywhere else in the tree.– Patrick Mevzek
Jun 7 at 13:25
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f448253%2fhow-many-aliases-for-name-linux-dns-can-have%23new-answer', 'question_page');
);
Post as a guest
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
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
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
I don't see any limits in the RFC's or the Administrator Reference Manual, aside from the namespace; about 52 * 63^61 * 62, or 185425111912981041324061287925175521345487663317034711682482804955458584183314016917166136523981820833351257751912 entries.
– Jeff Schaller
Jun 6 at 17:49
@JeffSchaller, thats true, i don't find that in any of the RFC so far for BIND 9.
– user294110
Jun 6 at 17:57
Since any other domain anywhere in the tree could have
CNAME testhost.example.comI do not see how you could restrict the number of such records since they could be anywhere else in the tree.– Patrick Mevzek
Jun 7 at 13:25
@PatrickMevzek, that's what my Question is ? because that is not explicitly defined in BIND9 RFC anywhere though its there for BIND8. so, my doubt was about that same , however i tested adding 200 aliases /CNAME records and its successful in BIND9.
– user294110
Jun 7 at 17:51
You are mixing two things: at the DNS level, as protocol, since a CNAME record can reside in a completely separate node in the tree than its target it is surely impossible to restrict how many CNAME in total go to a specific target. At a specific namesever implementation of DNS, the number of CNAMEs in a given zone is not restricted, as any other records than CNAMEs are not restricted in numbers either, except by the usual underlying label limits of 63 characters, total length of 255, etc. But I suspect you have an underlying question below all of that (as noone hits those limits)...
– Patrick Mevzek
Jun 7 at 17:56