Could there be any issues using “ns” as a subdomain?
I want to setup a subdomain "ns" on my domain, but before I do want to double check if there could be any potential issues using such a subdomain.
For example ns.mywebsite.com
To my knowledge, there shouldn't be, but I know a lot of nameservers are just named ns#.domain.com (e.g. ns1.domain.com ns2.domain.com) so I don't know if that could cause any issues.
domains subdomain
add a comment |
I want to setup a subdomain "ns" on my domain, but before I do want to double check if there could be any potential issues using such a subdomain.
For example ns.mywebsite.com
To my knowledge, there shouldn't be, but I know a lot of nameservers are just named ns#.domain.com (e.g. ns1.domain.com ns2.domain.com) so I don't know if that could cause any issues.
domains subdomain
add a comment |
I want to setup a subdomain "ns" on my domain, but before I do want to double check if there could be any potential issues using such a subdomain.
For example ns.mywebsite.com
To my knowledge, there shouldn't be, but I know a lot of nameservers are just named ns#.domain.com (e.g. ns1.domain.com ns2.domain.com) so I don't know if that could cause any issues.
domains subdomain
I want to setup a subdomain "ns" on my domain, but before I do want to double check if there could be any potential issues using such a subdomain.
For example ns.mywebsite.com
To my knowledge, there shouldn't be, but I know a lot of nameservers are just named ns#.domain.com (e.g. ns1.domain.com ns2.domain.com) so I don't know if that could cause any issues.
domains subdomain
domains subdomain
asked Jan 18 at 0:36


TheRyan722TheRyan722
1082
1082
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Some subdomains are reserved for specific purposes in DNS, like _domainkey
for email authentication.
That being said, I don't believe that ns
is one of those reserved subdomains, so you should be able to use it for whatever you want.
Actually, after doing some more research it seems like as long as you stay away from underscores, you should be fine. (Underscores for actual hostnames seem to cause trouble anyways.)
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
|
show 1 more comment
There's no magic in the prefix names of a DNS entry. You can name them whatever you want. Obviously, some people will think name server as you've already pointed out but the DNS servers won't be confused.
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such asroot-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.
– Patrick Mevzek
Jan 22 at 15:12
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "45"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fwebmasters.stackexchange.com%2fquestions%2f120304%2fcould-there-be-any-issues-using-ns-as-a-subdomain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Some subdomains are reserved for specific purposes in DNS, like _domainkey
for email authentication.
That being said, I don't believe that ns
is one of those reserved subdomains, so you should be able to use it for whatever you want.
Actually, after doing some more research it seems like as long as you stay away from underscores, you should be fine. (Underscores for actual hostnames seem to cause trouble anyways.)
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
|
show 1 more comment
Some subdomains are reserved for specific purposes in DNS, like _domainkey
for email authentication.
That being said, I don't believe that ns
is one of those reserved subdomains, so you should be able to use it for whatever you want.
Actually, after doing some more research it seems like as long as you stay away from underscores, you should be fine. (Underscores for actual hostnames seem to cause trouble anyways.)
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
|
show 1 more comment
Some subdomains are reserved for specific purposes in DNS, like _domainkey
for email authentication.
That being said, I don't believe that ns
is one of those reserved subdomains, so you should be able to use it for whatever you want.
Actually, after doing some more research it seems like as long as you stay away from underscores, you should be fine. (Underscores for actual hostnames seem to cause trouble anyways.)
Some subdomains are reserved for specific purposes in DNS, like _domainkey
for email authentication.
That being said, I don't believe that ns
is one of those reserved subdomains, so you should be able to use it for whatever you want.
Actually, after doing some more research it seems like as long as you stay away from underscores, you should be fine. (Underscores for actual hostnames seem to cause trouble anyways.)
edited Jan 18 at 2:49
answered Jan 18 at 2:28


Maximillian LaumeisterMaximillian Laumeister
4,1531829
4,1531829
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
|
show 1 more comment
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
By the way, I was inspired by your question so I posed this more general one to Webmasters SE: List of reserved third-level DNS zones?
– Maximillian Laumeister
Jan 18 at 3:09
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
Underscores for actual hostnames don't just cause trouble, they're not permitted by the RFC.
– A C
Jan 18 at 5:42
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
@AC Like some schmuck at the ietf is gonna tell me how I'm allowed use my domain name. Hold my beer _.maxl.us
– Maximillian Laumeister
Jan 18 at 7:16
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
Okay so they won't give me an ssl cert for it and half the DNS resolvers won't resolve it. But my principle stands.
– Maximillian Laumeister
Jan 18 at 7:28
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
This comment chain is hilarious and should end up being posted somewhere.
– TheRyan722
Jan 18 at 11:44
|
show 1 more comment
There's no magic in the prefix names of a DNS entry. You can name them whatever you want. Obviously, some people will think name server as you've already pointed out but the DNS servers won't be confused.
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such asroot-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.
– Patrick Mevzek
Jan 22 at 15:12
add a comment |
There's no magic in the prefix names of a DNS entry. You can name them whatever you want. Obviously, some people will think name server as you've already pointed out but the DNS servers won't be confused.
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such asroot-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.
– Patrick Mevzek
Jan 22 at 15:12
add a comment |
There's no magic in the prefix names of a DNS entry. You can name them whatever you want. Obviously, some people will think name server as you've already pointed out but the DNS servers won't be confused.
There's no magic in the prefix names of a DNS entry. You can name them whatever you want. Obviously, some people will think name server as you've already pointed out but the DNS servers won't be confused.
answered Jan 18 at 2:23
TreborTrebor
28810
28810
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such asroot-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.
– Patrick Mevzek
Jan 22 at 15:12
add a comment |
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such asroot-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.
– Patrick Mevzek
Jan 22 at 15:12
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such as
root-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.– Patrick Mevzek
Jan 22 at 15:12
"There's no magic in the prefix names of a DNS entry." This is mostly right and will correspond to end-users experiment. However for troubleshooting there are now prefixes with specific semantics, see rfc-editor.org/rfc/rfc8509.txt. In short a name such as
root-key-sentinel-not-ta-<key-tag>
under specific circumstances will trigger specific behaviour.– Patrick Mevzek
Jan 22 at 15:12
add a comment |
Thanks for contributing an answer to Webmasters Stack Exchange!
- 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%2fwebmasters.stackexchange.com%2fquestions%2f120304%2fcould-there-be-any-issues-using-ns-as-a-subdomain%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