How do a browser find the destination of general address such as http://diskstation:5000?
During setting synology NAS I just get curious how it works.
The NAS can be accessed by another computer on the network with the address
"http://diskstation:5000"or "http://find.synology.com".
I don't know how this works...
I guessted that the NAS may get an arbitrary IP using DHCP (this might be also wrong), but... how that can be accessed with "http://diskstation:5000"?...
Can anyone help me to understand what is going on?
Thank you in advance.
networking home-networking nas
add a comment |
During setting synology NAS I just get curious how it works.
The NAS can be accessed by another computer on the network with the address
"http://diskstation:5000"or "http://find.synology.com".
I don't know how this works...
I guessted that the NAS may get an arbitrary IP using DHCP (this might be also wrong), but... how that can be accessed with "http://diskstation:5000"?...
Can anyone help me to understand what is going on?
Thank you in advance.
networking home-networking nas
add a comment |
During setting synology NAS I just get curious how it works.
The NAS can be accessed by another computer on the network with the address
"http://diskstation:5000"or "http://find.synology.com".
I don't know how this works...
I guessted that the NAS may get an arbitrary IP using DHCP (this might be also wrong), but... how that can be accessed with "http://diskstation:5000"?...
Can anyone help me to understand what is going on?
Thank you in advance.
networking home-networking nas
During setting synology NAS I just get curious how it works.
The NAS can be accessed by another computer on the network with the address
"http://diskstation:5000"or "http://find.synology.com".
I don't know how this works...
I guessted that the NAS may get an arbitrary IP using DHCP (this might be also wrong), but... how that can be accessed with "http://diskstation:5000"?...
Can anyone help me to understand what is going on?
Thank you in advance.
networking home-networking nas
networking home-networking nas
asked Dec 4 at 8:01
Seungpyo Hong
1
1
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There are several possibilities:
DHCP
DHCP clients often report their own hostname as part of the address lease request, and many home routers maintain an internal DNS domain (e.g. .lan
or .home
) based on these hostnames.
For example: When the device reports that its hostname is "diskstation" and obtains an address via DHCP, the router adds an internal DNS entry diskstation.home
with the address it leased.
When your computer obtains an address via DHCP, the router also informs that the local DNS suffix is ".home" and therefore diskstation
should be expanded to diskstation.home
, which then can be resolved through the router's internal DNS server.
Local names
Many devices support serverless name resolution using Apple's mDNS, Microsoft's NetBIOS or LLMNR. When the browser needs to resolve a dotless name like diskstation
, instead of asking DNS the operating system broadcasts the query on the local LAN network and waits for any random device to reply.
I don't know whether Synology NAS firmware supports LLMNR or NetBIOS, but it certainly supports mDNS. Generally mDNS names are always in the form of <name>.local
instead of dotless, but the recently-added mDNS implementation in Windows 10 actually accepts both versions.
Website
Finally, the "find.synology.com" website does nothing magic at all. It just tries to redirect you to the first address you mentioned (http://diskstation.local:5000
). If that doesn't work, it redirects to http://rackstation.local:5000
, then to http://synologyrouter.local:5000
, and so on. Either it finds the correct address by trial-and-error or it doesn't.
Of course, for this to work, one of the above methods (mDNS or LLMNR) must already be active.
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
add a comment |
I can't add any additional information to grawity's answer, but your router is the place where you're most likely to find out. (Enter the IP into your browser)
Windows:
ipconfig | findstr /i "Gateway"
*nix:
ip route | grep default
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%2f1380617%2fhow-do-a-browser-find-the-destination-of-general-address-such-as-http-diskstat%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
There are several possibilities:
DHCP
DHCP clients often report their own hostname as part of the address lease request, and many home routers maintain an internal DNS domain (e.g. .lan
or .home
) based on these hostnames.
For example: When the device reports that its hostname is "diskstation" and obtains an address via DHCP, the router adds an internal DNS entry diskstation.home
with the address it leased.
When your computer obtains an address via DHCP, the router also informs that the local DNS suffix is ".home" and therefore diskstation
should be expanded to diskstation.home
, which then can be resolved through the router's internal DNS server.
Local names
Many devices support serverless name resolution using Apple's mDNS, Microsoft's NetBIOS or LLMNR. When the browser needs to resolve a dotless name like diskstation
, instead of asking DNS the operating system broadcasts the query on the local LAN network and waits for any random device to reply.
I don't know whether Synology NAS firmware supports LLMNR or NetBIOS, but it certainly supports mDNS. Generally mDNS names are always in the form of <name>.local
instead of dotless, but the recently-added mDNS implementation in Windows 10 actually accepts both versions.
Website
Finally, the "find.synology.com" website does nothing magic at all. It just tries to redirect you to the first address you mentioned (http://diskstation.local:5000
). If that doesn't work, it redirects to http://rackstation.local:5000
, then to http://synologyrouter.local:5000
, and so on. Either it finds the correct address by trial-and-error or it doesn't.
Of course, for this to work, one of the above methods (mDNS or LLMNR) must already be active.
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
add a comment |
There are several possibilities:
DHCP
DHCP clients often report their own hostname as part of the address lease request, and many home routers maintain an internal DNS domain (e.g. .lan
or .home
) based on these hostnames.
For example: When the device reports that its hostname is "diskstation" and obtains an address via DHCP, the router adds an internal DNS entry diskstation.home
with the address it leased.
When your computer obtains an address via DHCP, the router also informs that the local DNS suffix is ".home" and therefore diskstation
should be expanded to diskstation.home
, which then can be resolved through the router's internal DNS server.
Local names
Many devices support serverless name resolution using Apple's mDNS, Microsoft's NetBIOS or LLMNR. When the browser needs to resolve a dotless name like diskstation
, instead of asking DNS the operating system broadcasts the query on the local LAN network and waits for any random device to reply.
I don't know whether Synology NAS firmware supports LLMNR or NetBIOS, but it certainly supports mDNS. Generally mDNS names are always in the form of <name>.local
instead of dotless, but the recently-added mDNS implementation in Windows 10 actually accepts both versions.
Website
Finally, the "find.synology.com" website does nothing magic at all. It just tries to redirect you to the first address you mentioned (http://diskstation.local:5000
). If that doesn't work, it redirects to http://rackstation.local:5000
, then to http://synologyrouter.local:5000
, and so on. Either it finds the correct address by trial-and-error or it doesn't.
Of course, for this to work, one of the above methods (mDNS or LLMNR) must already be active.
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
add a comment |
There are several possibilities:
DHCP
DHCP clients often report their own hostname as part of the address lease request, and many home routers maintain an internal DNS domain (e.g. .lan
or .home
) based on these hostnames.
For example: When the device reports that its hostname is "diskstation" and obtains an address via DHCP, the router adds an internal DNS entry diskstation.home
with the address it leased.
When your computer obtains an address via DHCP, the router also informs that the local DNS suffix is ".home" and therefore diskstation
should be expanded to diskstation.home
, which then can be resolved through the router's internal DNS server.
Local names
Many devices support serverless name resolution using Apple's mDNS, Microsoft's NetBIOS or LLMNR. When the browser needs to resolve a dotless name like diskstation
, instead of asking DNS the operating system broadcasts the query on the local LAN network and waits for any random device to reply.
I don't know whether Synology NAS firmware supports LLMNR or NetBIOS, but it certainly supports mDNS. Generally mDNS names are always in the form of <name>.local
instead of dotless, but the recently-added mDNS implementation in Windows 10 actually accepts both versions.
Website
Finally, the "find.synology.com" website does nothing magic at all. It just tries to redirect you to the first address you mentioned (http://diskstation.local:5000
). If that doesn't work, it redirects to http://rackstation.local:5000
, then to http://synologyrouter.local:5000
, and so on. Either it finds the correct address by trial-and-error or it doesn't.
Of course, for this to work, one of the above methods (mDNS or LLMNR) must already be active.
There are several possibilities:
DHCP
DHCP clients often report their own hostname as part of the address lease request, and many home routers maintain an internal DNS domain (e.g. .lan
or .home
) based on these hostnames.
For example: When the device reports that its hostname is "diskstation" and obtains an address via DHCP, the router adds an internal DNS entry diskstation.home
with the address it leased.
When your computer obtains an address via DHCP, the router also informs that the local DNS suffix is ".home" and therefore diskstation
should be expanded to diskstation.home
, which then can be resolved through the router's internal DNS server.
Local names
Many devices support serverless name resolution using Apple's mDNS, Microsoft's NetBIOS or LLMNR. When the browser needs to resolve a dotless name like diskstation
, instead of asking DNS the operating system broadcasts the query on the local LAN network and waits for any random device to reply.
I don't know whether Synology NAS firmware supports LLMNR or NetBIOS, but it certainly supports mDNS. Generally mDNS names are always in the form of <name>.local
instead of dotless, but the recently-added mDNS implementation in Windows 10 actually accepts both versions.
Website
Finally, the "find.synology.com" website does nothing magic at all. It just tries to redirect you to the first address you mentioned (http://diskstation.local:5000
). If that doesn't work, it redirects to http://rackstation.local:5000
, then to http://synologyrouter.local:5000
, and so on. Either it finds the correct address by trial-and-error or it doesn't.
Of course, for this to work, one of the above methods (mDNS or LLMNR) must already be active.
answered Dec 4 at 8:20
grawity
232k35490546
232k35490546
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
add a comment |
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
Thank you so much!!! I was somewhat overwhelmed by your thorough and kind answers. ^^; I learned a lot. Thank you!
– Seungpyo Hong
Dec 6 at 4:58
add a comment |
I can't add any additional information to grawity's answer, but your router is the place where you're most likely to find out. (Enter the IP into your browser)
Windows:
ipconfig | findstr /i "Gateway"
*nix:
ip route | grep default
add a comment |
I can't add any additional information to grawity's answer, but your router is the place where you're most likely to find out. (Enter the IP into your browser)
Windows:
ipconfig | findstr /i "Gateway"
*nix:
ip route | grep default
add a comment |
I can't add any additional information to grawity's answer, but your router is the place where you're most likely to find out. (Enter the IP into your browser)
Windows:
ipconfig | findstr /i "Gateway"
*nix:
ip route | grep default
I can't add any additional information to grawity's answer, but your router is the place where you're most likely to find out. (Enter the IP into your browser)
Windows:
ipconfig | findstr /i "Gateway"
*nix:
ip route | grep default
answered Dec 4 at 9:23
manavortex
11
11
add a comment |
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.
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%2fsuperuser.com%2fquestions%2f1380617%2fhow-do-a-browser-find-the-destination-of-general-address-such-as-http-diskstat%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