Enforce the usage of a different DNS domain for servicePrincipalNames
For mostly historic reasons our default DNS domain (lets call it new.example.net) differs from our Kerberos REALM (OLD.EXAMPLE.COM)
Actually the KDC (an Active Directory Server) does not know about this newer domain at all.
In Linux clients this seems to get a problem when trying to access a source on "server1.new.example.net".
The client will try to request a Service principle of the following form:
cifs/server1.new.example.net@OLD.EXAMPLE.COM
This will not work as valid servicePrincipalNames would only be:
cifs/server1@OLD.EXAMPLE.COM and cifs/server1.old.example.com@OLD.EXAMPLE.COM
Unfortunately I did not find an option for krb5.com to do some domain mapping for servicePrincipalNames to enforce a FQDN of "old.example.com" in any case.
Any Idea?
kerberos
add a comment |
For mostly historic reasons our default DNS domain (lets call it new.example.net) differs from our Kerberos REALM (OLD.EXAMPLE.COM)
Actually the KDC (an Active Directory Server) does not know about this newer domain at all.
In Linux clients this seems to get a problem when trying to access a source on "server1.new.example.net".
The client will try to request a Service principle of the following form:
cifs/server1.new.example.net@OLD.EXAMPLE.COM
This will not work as valid servicePrincipalNames would only be:
cifs/server1@OLD.EXAMPLE.COM and cifs/server1.old.example.com@OLD.EXAMPLE.COM
Unfortunately I did not find an option for krb5.com to do some domain mapping for servicePrincipalNames to enforce a FQDN of "old.example.com" in any case.
Any Idea?
kerberos
add a comment |
For mostly historic reasons our default DNS domain (lets call it new.example.net) differs from our Kerberos REALM (OLD.EXAMPLE.COM)
Actually the KDC (an Active Directory Server) does not know about this newer domain at all.
In Linux clients this seems to get a problem when trying to access a source on "server1.new.example.net".
The client will try to request a Service principle of the following form:
cifs/server1.new.example.net@OLD.EXAMPLE.COM
This will not work as valid servicePrincipalNames would only be:
cifs/server1@OLD.EXAMPLE.COM and cifs/server1.old.example.com@OLD.EXAMPLE.COM
Unfortunately I did not find an option for krb5.com to do some domain mapping for servicePrincipalNames to enforce a FQDN of "old.example.com" in any case.
Any Idea?
kerberos
For mostly historic reasons our default DNS domain (lets call it new.example.net) differs from our Kerberos REALM (OLD.EXAMPLE.COM)
Actually the KDC (an Active Directory Server) does not know about this newer domain at all.
In Linux clients this seems to get a problem when trying to access a source on "server1.new.example.net".
The client will try to request a Service principle of the following form:
cifs/server1.new.example.net@OLD.EXAMPLE.COM
This will not work as valid servicePrincipalNames would only be:
cifs/server1@OLD.EXAMPLE.COM and cifs/server1.old.example.com@OLD.EXAMPLE.COM
Unfortunately I did not find an option for krb5.com to do some domain mapping for servicePrincipalNames to enforce a FQDN of "old.example.com" in any case.
Any Idea?
kerberos
kerberos
asked Dec 11 at 13:28
Sven Geggus
3861210
3861210
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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%2funix.stackexchange.com%2fquestions%2f487345%2fenforce-the-usage-of-a-different-dns-domain-for-serviceprincipalnames%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux 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.
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%2funix.stackexchange.com%2fquestions%2f487345%2fenforce-the-usage-of-a-different-dns-domain-for-serviceprincipalnames%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