3 ms·
Those go to the same place for me
by trocadero 8y ago
Those go to the same place for me
- deleted 8y ago[deleted]
- dsl 8y agoSome small subset of pool servers run an HTTP server that redirects you to www. Not all of them. You just got lucky.
- euyyn 8y agoI must be lucky too, as I got the same result from both.
- Volundr 8y agoThat's exactly right. www.pool.ntp.org is the project site. pool.ntp.org is for getting an NTP server. Which one you get will depend on your location and random chance. That server will run NTP, but what it happens to run on port 80, if anything, is up to the operator of the server.
- drb91 8y agoThey definitely do not for me (ios).
- da_chicken 8y agoNot me. http://www.pool.ntp.org/ http://www.pool.ntp.org/ redirects me to https://www.ntppool.org/en/ https://www.ntppool.org/en/. http://pool.ntp.org/ http://pool.ntp.org/ takes me to an "It works!" default Apache 2 page for an Ubuntu installation. As the comment in the issue describes, http://pool.ntp.org/ http://pool.ntp.org/ takes you to a random ntp server. If you want another example, try google.com using Google's own DNS: PS U:\> nslookup - 8.8.8.8 Default Server: google-public-dns-a.google.com Address: 8.8.8.8 > google.com Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: google.com Addresses: 2607:f8b0:4009:810::200e 172.217.8.206 > www.google.com Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: forcesafesearch.google.com Addresses: 216.239.38.120 216.239.38.120 Aliases: www.google.com Even if you ultimately end up at the same site through redirects, you're clearly not going to the same site initially.
- trocadero 8y ago>http://pool.ntp.org/ http://pool.ntp.org/ takes me to an "It works!" default Apache 2 page for an Ubuntu installation. As the comment in the issue describes, http://pool.ntp.org/ http://pool.ntp.org/ takes you to a random ntp server. Either way, the ask was for a difference in www.example.com vs example.com. Not a difference in www.pool.example.com vs pool.example.com. In the latter case, the different subdomains will still be shown (AFAIK). >Even if you ultimately end up at the same site through redirects, you're clearly not going to the same site initially. Which is nothing that an end user is going to care about and doesn't provide an example to the asked question.
- Nadya 8y ago>In the latter case, the different subdomains will still be shown (AFAIK). http://www.pool.example.com http://www.pool.example.com displays as http://pool.example.com http://pool.example.com Here's a gif: https://vgy.me/61I0DA.gif https://vgy.me/61I0DA.gif For fun I'm going to set up a www.www.www.www.www.www.www.www.www record. http://www.www.www.www.www.www.www.www.www.www.example.com http://www.www.www.www.www.www.www.www.www.www.example.com shows as example.com E: I'll add it to my certs later but I did it: https://www.www.www.www.www.www.www.www.www.www.www.www.aishitei.ru https://www.www.www.www.www.www.www.www.www.www.www.www.aish... E2: http://www.example.www.example.org http://www.example.www.example.org shows up as example.example.org - this is fun.
- warent 8y agoRe: E2 (http://www.example.www.example.org http://www.example.www.example.org === example.example.org) I just found the same thing. How exactly is this a feature? What an insane decision.
- zaarn 8y agoThat is absolutely insane and someone should be fired and shamed for this. I didn't like just trimming a pure www. but trimming any www. in the hostname is just dumb behaviour. How would I differentiate between loadbalancer1.www.intranet and loadbalancer1.intranet? THOSE ARE NOT THE SAME.