DNS name not resolved
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
We have a server machine with IP address = 192.168.90.6. On this machine we have installed DNS and Domain Controller and DNS is integrated with AD (ad.corp.com).
Case 1: When machine joins with ad.corp.com, then there is no issue.
Case 2: When machine doesn't join with ad.corp.com, then problem happens, i.e. we cannot access domain machine by using its name. But when IP address is used, it works properly.
I want to know how we can change the setting of DNS Server to resolve Case 2 issue?
Result of nslookup
on client machine is as per below:
C:Usersabc>nslookup - 192.168.90.6
Default Server: UnKnown
Address: 192.168.90.6
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
dns
add a comment |
We have a server machine with IP address = 192.168.90.6. On this machine we have installed DNS and Domain Controller and DNS is integrated with AD (ad.corp.com).
Case 1: When machine joins with ad.corp.com, then there is no issue.
Case 2: When machine doesn't join with ad.corp.com, then problem happens, i.e. we cannot access domain machine by using its name. But when IP address is used, it works properly.
I want to know how we can change the setting of DNS Server to resolve Case 2 issue?
Result of nslookup
on client machine is as per below:
C:Usersabc>nslookup - 192.168.90.6
Default Server: UnKnown
Address: 192.168.90.6
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
dns
add a comment |
We have a server machine with IP address = 192.168.90.6. On this machine we have installed DNS and Domain Controller and DNS is integrated with AD (ad.corp.com).
Case 1: When machine joins with ad.corp.com, then there is no issue.
Case 2: When machine doesn't join with ad.corp.com, then problem happens, i.e. we cannot access domain machine by using its name. But when IP address is used, it works properly.
I want to know how we can change the setting of DNS Server to resolve Case 2 issue?
Result of nslookup
on client machine is as per below:
C:Usersabc>nslookup - 192.168.90.6
Default Server: UnKnown
Address: 192.168.90.6
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
dns
We have a server machine with IP address = 192.168.90.6. On this machine we have installed DNS and Domain Controller and DNS is integrated with AD (ad.corp.com).
Case 1: When machine joins with ad.corp.com, then there is no issue.
Case 2: When machine doesn't join with ad.corp.com, then problem happens, i.e. we cannot access domain machine by using its name. But when IP address is used, it works properly.
I want to know how we can change the setting of DNS Server to resolve Case 2 issue?
Result of nslookup
on client machine is as per below:
C:Usersabc>nslookup - 192.168.90.6
Default Server: UnKnown
Address: 192.168.90.6
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
dns
dns
edited Aug 1 '12 at 10:14
jokerdino
2,26211932
2,26211932
asked Aug 1 '12 at 10:04
Acty SystemActy System
1112
1112
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
0)
ad.corp.com
The corp.com domain is owned by Mike O'Connor who isn't currently using it for much. If you are also using that domain internally you have a recipe for future confusion when Mike sells it to someone or starts using it in earnest (or even now).
1)
Default Server: UnKnown
Address: 192.168.90.6
Your DNS server at 192.168.90.6 doesn't know who it is!
It lacks a PTR record in a 192.168.90 zonefile
6 IN PTR dc1.example.com.
or MS equivalent.
I recommend you register a domain for your company and use it internally using a split-horizon DNS setup. Or pay a consultant to advise.
2)
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
Your DNS server has no idea what DNS domain to append to incomplete queries
These are all fairly fundamental issues suggesting that whoever set this up needs more training or to call in a consultant.
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
add a comment |
You should configure your "DNS Server's IP" as prefered DNS Server at your un-joined client first. It should work.
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f456208%2fdns-name-not-resolved%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
0)
ad.corp.com
The corp.com domain is owned by Mike O'Connor who isn't currently using it for much. If you are also using that domain internally you have a recipe for future confusion when Mike sells it to someone or starts using it in earnest (or even now).
1)
Default Server: UnKnown
Address: 192.168.90.6
Your DNS server at 192.168.90.6 doesn't know who it is!
It lacks a PTR record in a 192.168.90 zonefile
6 IN PTR dc1.example.com.
or MS equivalent.
I recommend you register a domain for your company and use it internally using a split-horizon DNS setup. Or pay a consultant to advise.
2)
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
Your DNS server has no idea what DNS domain to append to incomplete queries
These are all fairly fundamental issues suggesting that whoever set this up needs more training or to call in a consultant.
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
add a comment |
0)
ad.corp.com
The corp.com domain is owned by Mike O'Connor who isn't currently using it for much. If you are also using that domain internally you have a recipe for future confusion when Mike sells it to someone or starts using it in earnest (or even now).
1)
Default Server: UnKnown
Address: 192.168.90.6
Your DNS server at 192.168.90.6 doesn't know who it is!
It lacks a PTR record in a 192.168.90 zonefile
6 IN PTR dc1.example.com.
or MS equivalent.
I recommend you register a domain for your company and use it internally using a split-horizon DNS setup. Or pay a consultant to advise.
2)
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
Your DNS server has no idea what DNS domain to append to incomplete queries
These are all fairly fundamental issues suggesting that whoever set this up needs more training or to call in a consultant.
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
add a comment |
0)
ad.corp.com
The corp.com domain is owned by Mike O'Connor who isn't currently using it for much. If you are also using that domain internally you have a recipe for future confusion when Mike sells it to someone or starts using it in earnest (or even now).
1)
Default Server: UnKnown
Address: 192.168.90.6
Your DNS server at 192.168.90.6 doesn't know who it is!
It lacks a PTR record in a 192.168.90 zonefile
6 IN PTR dc1.example.com.
or MS equivalent.
I recommend you register a domain for your company and use it internally using a split-horizon DNS setup. Or pay a consultant to advise.
2)
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
Your DNS server has no idea what DNS domain to append to incomplete queries
These are all fairly fundamental issues suggesting that whoever set this up needs more training or to call in a consultant.
0)
ad.corp.com
The corp.com domain is owned by Mike O'Connor who isn't currently using it for much. If you are also using that domain internally you have a recipe for future confusion when Mike sells it to someone or starts using it in earnest (or even now).
1)
Default Server: UnKnown
Address: 192.168.90.6
Your DNS server at 192.168.90.6 doesn't know who it is!
It lacks a PTR record in a 192.168.90 zonefile
6 IN PTR dc1.example.com.
or MS equivalent.
I recommend you register a domain for your company and use it internally using a split-horizon DNS setup. Or pay a consultant to advise.
2)
> dc1
Server: UnKnown
Address: 192.168.90.6
*** UnKnown can't find dc1: Server failed
Your DNS server has no idea what DNS domain to append to incomplete queries
These are all fairly fundamental issues suggesting that whoever set this up needs more training or to call in a consultant.
edited Aug 1 '12 at 11:20
answered Aug 1 '12 at 11:14
RedGrittyBrickRedGrittyBrick
67.5k13106164
67.5k13106164
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
add a comment |
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
Thanks RedGrittyBrick for you reply, I want to clear my issue again so that you know the exact problem. When my client machine Joined with domain ad.corp.com then nslookup result is as per below C:Usersabc>nslookup - 192.168.90.6 Default Server: UnKnown Address: 192.168.90.6 > dc1 Server: UnKnown Address: 192.168.90.6 Name: dc1.ad.acty-sys.co.in Address: 192.168.90.225
– Acty System
Aug 1 '12 at 11:21
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
BUT when I UNJOINED Client machine with domain ad.corp.com then it gives following result ..... > dc1 Server: UnKnown Address: 192.168.90.6 *** UnKnown can't find dc1: Server failed I am facing this problem, hope you understand my problem. Please kindly help me for the same.
– Acty System
Aug 1 '12 at 11:31
add a comment |
You should configure your "DNS Server's IP" as prefered DNS Server at your un-joined client first. It should work.
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
add a comment |
You should configure your "DNS Server's IP" as prefered DNS Server at your un-joined client first. It should work.
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
add a comment |
You should configure your "DNS Server's IP" as prefered DNS Server at your un-joined client first. It should work.
You should configure your "DNS Server's IP" as prefered DNS Server at your un-joined client first. It should work.
answered Aug 2 '12 at 7:01
Rajendra RathoreRajendra Rathore
16015
16015
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
add a comment |
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
Thanks Rajendra for your reply I have configured my client machine with DNS Server's IP as prefered DNS server but still it is not working. Result of nslookup is same as above.
– Acty System
Aug 3 '12 at 4:32
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
@Acty System: - Please perform a cross check that, Did you created associate PTR records in DNS Server? and please use Server's FQDN for accessing it from outsite or unjoined clients. Such as : - (dc1.example.local)
– Rajendra Rathore
Aug 3 '12 at 17:33
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f456208%2fdns-name-not-resolved%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