Why cannot I ping computer name without dot?
In my home network I have a dhcp server and a dns server running on a router.
Dhcp and internet access are working fine.
I have for each device on my home network a dns record that associate some name to the device ip address.
For example mycomputer resolves to 192.168.0.111.
However when I issue at command line in Windows 10:
ping mycomputer
I'm getting
Ping request could not find host mycomputer. Please check the name and try again.
I think this is a windows problem, not a router or configuration problem. This is because:
ping mycomputerworks perfectly from ubuntu- if I create a dns record like
mycomputer.localor evenmycomputer.blaand assign this to the same ip address I canping mycomputre.localorping mycomputre.blafrom Windows 10 without an issue. - Finally,
ping mycomputer.(note the dot at the end) also works in Windows 10. - If I look at the traffic in Wireshark, I can see that
ping mycomputer.localresults in a DNS request whileping mycomputerdoes not.
It appears that if the target computer name is not multi-part, windows will not resolve it unless I add the dot at the end. This effect does not happen for multi-part names.
I would like to understand: Why is this the case?
networking windows-10 dns
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
|
show 7 more comments
In my home network I have a dhcp server and a dns server running on a router.
Dhcp and internet access are working fine.
I have for each device on my home network a dns record that associate some name to the device ip address.
For example mycomputer resolves to 192.168.0.111.
However when I issue at command line in Windows 10:
ping mycomputer
I'm getting
Ping request could not find host mycomputer. Please check the name and try again.
I think this is a windows problem, not a router or configuration problem. This is because:
ping mycomputerworks perfectly from ubuntu- if I create a dns record like
mycomputer.localor evenmycomputer.blaand assign this to the same ip address I canping mycomputre.localorping mycomputre.blafrom Windows 10 without an issue. - Finally,
ping mycomputer.(note the dot at the end) also works in Windows 10. - If I look at the traffic in Wireshark, I can see that
ping mycomputer.localresults in a DNS request whileping mycomputerdoes not.
It appears that if the target computer name is not multi-part, windows will not resolve it unless I add the dot at the end. This effect does not happen for multi-part names.
I would like to understand: Why is this the case?
networking windows-10 dns
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
You have a Windows machine without a DNS suffix? Can you postipconfig /all?
– Paul
May 19 '16 at 1:04
1
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16
|
show 7 more comments
In my home network I have a dhcp server and a dns server running on a router.
Dhcp and internet access are working fine.
I have for each device on my home network a dns record that associate some name to the device ip address.
For example mycomputer resolves to 192.168.0.111.
However when I issue at command line in Windows 10:
ping mycomputer
I'm getting
Ping request could not find host mycomputer. Please check the name and try again.
I think this is a windows problem, not a router or configuration problem. This is because:
ping mycomputerworks perfectly from ubuntu- if I create a dns record like
mycomputer.localor evenmycomputer.blaand assign this to the same ip address I canping mycomputre.localorping mycomputre.blafrom Windows 10 without an issue. - Finally,
ping mycomputer.(note the dot at the end) also works in Windows 10. - If I look at the traffic in Wireshark, I can see that
ping mycomputer.localresults in a DNS request whileping mycomputerdoes not.
It appears that if the target computer name is not multi-part, windows will not resolve it unless I add the dot at the end. This effect does not happen for multi-part names.
I would like to understand: Why is this the case?
networking windows-10 dns
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
In my home network I have a dhcp server and a dns server running on a router.
Dhcp and internet access are working fine.
I have for each device on my home network a dns record that associate some name to the device ip address.
For example mycomputer resolves to 192.168.0.111.
However when I issue at command line in Windows 10:
ping mycomputer
I'm getting
Ping request could not find host mycomputer. Please check the name and try again.
I think this is a windows problem, not a router or configuration problem. This is because:
ping mycomputerworks perfectly from ubuntu- if I create a dns record like
mycomputer.localor evenmycomputer.blaand assign this to the same ip address I canping mycomputre.localorping mycomputre.blafrom Windows 10 without an issue. - Finally,
ping mycomputer.(note the dot at the end) also works in Windows 10. - If I look at the traffic in Wireshark, I can see that
ping mycomputer.localresults in a DNS request whileping mycomputerdoes not.
It appears that if the target computer name is not multi-part, windows will not resolve it unless I add the dot at the end. This effect does not happen for multi-part names.
I would like to understand: Why is this the case?
networking windows-10 dns
networking windows-10 dns
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
edited May 19 '16 at 0:40
Andrew Savinykh
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
asked May 19 '16 at 0:27
Andrew SavinykhAndrew Savinykh
95731728
95731728
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
You have a Windows machine without a DNS suffix? Can you postipconfig /all?
– Paul
May 19 '16 at 1:04
1
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16
|
show 7 more comments
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
You have a Windows machine without a DNS suffix? Can you postipconfig /all?
– Paul
May 19 '16 at 1:04
1
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
You have a Windows machine without a DNS suffix? Can you post
ipconfig /all?– Paul
May 19 '16 at 1:04
You have a Windows machine without a DNS suffix? Can you post
ipconfig /all?– Paul
May 19 '16 at 1:04
1
1
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16
|
show 7 more comments
1 Answer
1
active
oldest
votes
You probably do not have a WINS server on the network. Windows first tries WINS server for single part names, because it assumes that these are NetBIOS names and when it fails it does not try DNS.
According to Resolving names article, WINS is the first thing to check, however a subsequent step are supposed to make a DNS query. It's possible that since this particular article does not go into a lot of details, there are some conditions that are being met, that aborts the resolution process before it reaches the DNS step.
This is a longer article on the subject.
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
|
show 3 more comments
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%2f1078467%2fwhy-cannot-i-ping-computer-name-without-dot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You probably do not have a WINS server on the network. Windows first tries WINS server for single part names, because it assumes that these are NetBIOS names and when it fails it does not try DNS.
According to Resolving names article, WINS is the first thing to check, however a subsequent step are supposed to make a DNS query. It's possible that since this particular article does not go into a lot of details, there are some conditions that are being met, that aborts the resolution process before it reaches the DNS step.
This is a longer article on the subject.
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
|
show 3 more comments
You probably do not have a WINS server on the network. Windows first tries WINS server for single part names, because it assumes that these are NetBIOS names and when it fails it does not try DNS.
According to Resolving names article, WINS is the first thing to check, however a subsequent step are supposed to make a DNS query. It's possible that since this particular article does not go into a lot of details, there are some conditions that are being met, that aborts the resolution process before it reaches the DNS step.
This is a longer article on the subject.
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
|
show 3 more comments
You probably do not have a WINS server on the network. Windows first tries WINS server for single part names, because it assumes that these are NetBIOS names and when it fails it does not try DNS.
According to Resolving names article, WINS is the first thing to check, however a subsequent step are supposed to make a DNS query. It's possible that since this particular article does not go into a lot of details, there are some conditions that are being met, that aborts the resolution process before it reaches the DNS step.
This is a longer article on the subject.
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
You probably do not have a WINS server on the network. Windows first tries WINS server for single part names, because it assumes that these are NetBIOS names and when it fails it does not try DNS.
According to Resolving names article, WINS is the first thing to check, however a subsequent step are supposed to make a DNS query. It's possible that since this particular article does not go into a lot of details, there are some conditions that are being met, that aborts the resolution process before it reaches the DNS step.
This is a longer article on the subject.
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
answered May 19 '16 at 0:48
Andrew SavinykhAndrew Savinykh
95731728
95731728
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
|
show 3 more comments
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
Note that WINS is only required for NetBIOS operations across subnets, and that article is only pertinent to the 2003 and prior lines of windows (xp, server 2k3, etc). NBT (NetBIOS over TCP) will largely replace the need for WINS.
– Frank Thomas
May 19 '16 at 2:18
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@FrankThomas, are you saying that Windows 10 is not try using WINS at all by default? If that's the case it's a useful piece of information.
– Andrew Savinykh
May 19 '16 at 2:30
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
@zespri Does this answer mean you have solved it? It doesn't appear to be an answer to your question, rather it looks more like information that should be added to the question.
– Paul
May 19 '16 at 2:49
1
1
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
Windows will only use WINS for lookup if a WINS server IP address is entered in the Network Adapter settings -> IPv4 -> Advanced -> WINS. NetBIOS is a modern version of the NetBEUI protocol, which could not be carrier across a router, because of the way it used broadcasts for browser role elections and browse list access. These mechanisms are still in play, even today, but with a new fancy TCP wrapper, so you don't need WINS to enable traffic across IP routers.
– Frank Thomas
May 19 '16 at 2:53
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
@FrankThomas, thank you for sharing this. Would it be fair to assume that in my case Windows attempts NetBIOS resolution and when this does not work it bails instead of trying DNS?
– Andrew Savinykh
May 19 '16 at 3:32
|
show 3 more comments
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%2f1078467%2fwhy-cannot-i-ping-computer-name-without-dot%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
This looks relevant
– Andrew Savinykh
May 19 '16 at 0:34
Probably a mismatch between the dns suffix on your network vs the dns suffix on the router (ie the router doesn't have one). If your home network dns suffix is .local, make the router suffix the same.
– Paul
May 19 '16 at 0:39
@Paul there is no home network suffix as far as I can see. I edited the question to clarify that it's not 'local' what makes it work it's any suffix.
– Andrew Savinykh
May 19 '16 at 0:41
You have a Windows machine without a DNS suffix? Can you post
ipconfig /all?– Paul
May 19 '16 at 1:04
1
Turn off (uncheck) your ip6 on your network device.
– GeekyDaddy
May 19 '16 at 2:16