7 ms·
>there's a difference between "www.example.com" and "example.com" Can you link to a site where these two are different?
by trocadero 8y ago
>there's a difference between "www.example.com" and "example.com"
Can you link to a site where these two are different?
- deleted 8y ago[deleted]
- geophertz 8y agowww.pool.ntp.org pool.ntp.org
- ddebernardy 8y agoFrom one of the comments there: http://www.pool.ntp.org http://www.pool.ntp.org vs http://pool.ntp.org http://pool.ntp.org One takes you to the website about the project, the other goes to a random ntp server.
- trocadero 8y agoThose 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.
- deleted 8y ago[deleted]
- drbawb 8y agoOK, which one of you hooligans runs this NTP server[1] that plays some loud obnoxious dubstep track? [1]: https://i.imgur.com/cEukhNu.jpg https://i.imgur.com/cEukhNu.jpg
- runjake 8y agoMany orgs do this. For example, with Active Directory, the DNS A record for your foo.com domain must resolve to your domain controllers. Your www.foo.com will resolve to a separate non-domain controller web server. I think a lot of the commenters here are thinking solely in terms of commercial web services such as twitter.com and such, but there's so much more to the wider landscape.
- EvanAnderson 8y agoThinking about it that way gives me conflicted feelings. Much as I hate what Google has done here I also feel like any organization stupid enough to use their public domain name for their Active Directory domain name deserves every little pain they receive for it.
- tatersolid 8y agoYou lack the compassion that comes with experience. My $dayjob has our AD root domain the same as our public root domain. Because we implemented AD in the year 2000, and this was Microsoft’s recommendation for domain naming way back then. And if you use Exchange, you can’t rename your AD domain, you have to rebuild your forest and migrate piecemeal. So we’re stuck with it. The practice of using Corp.example.com did not evolve until many years after Windows 2000 and Exchange 2000 were in the wild. So we run http redirectors on each of our domain controllers to send traffic to www.
- EvanAnderson 8y agoThis one is kind of a "religious" topic for me, I guess. I'm sorry that it is, but it makes me exceedingly defensive. I trained on Active Directory (AD) with a group of veteran sysadmins in 1999. I don't have access to the "Microsoft Official Curriculum" book from my class in '99 (long-since thrown away), but I have a distinct memory of a lively conversation in class re: the pitfalls of using a public domain name as an AD domain name (or, worse yet, a Forest Root domain name) during the class. It was very evident to our group of veteran sysadmins that using a public domain name in AD would create silly make-work scenarios (like installing IIS on every DC just to run redirect visitors to "www.example.com"-- just as you describe, albeit IIS didn't natively support sending redirects at the time). I'd go further and suggest that anybody with a modicum of familiarity with DNS knows having multiple roots-of-authority for a single domain name is a bad idea. Microsoft not supporting split-horizon in their DNS server (like BIND does with 'views') compounded the difficulties with such a scenario in an all-Windows environment. I certainly wouldn't argue that Microsoft has given exclusively good recommendations for AD domain names in the past (evidence ".local" in Windows Small Business Server), but I am reasonably certain that their documentation always suggested that using a subdomain of a public domain name was a supported and workable option. I started deploying AD in 2000. I've deployed roughly 50 forests in different enterprises, and I've never used a public domain name as an AD domain name. I've domain-renamed all my subsequently-acquired Customers for whom it was an option (which it was, so long as they had not yet installed Exchange 2007), and have been rebuilding the Forests of Customers who made the wrong decision in the past, where it makes economical sense.
- acdanger 8y agoMany companies have their marketing site at www. and they're app at at, say, app. e.g. https://www.netlify.com/ https://www.netlify.com/ vs https://app.netlify.com/ https://app.netlify.com/
- kageneko 8y agoI don't remember the site offhand, but I was going to one recently where example.com didn't even work, it was some weird error page -- you had to use www.example.com. If it comes to me, I'll post it.
- richrichardsson 8y agoI've seen this behaviour, and the reverse. Can't remember examples, but it does happen.
- baby 8y agoThis is what Chrome's update is trying to fix. Developers are confuser when setting up dns if they should have www or not have www or only have www...
- martimarkov 8y agoNot really fixing it thou because they just strip the www part from the name. If the developer does not setup www.domain.com and the user goes there chrome will not “fix” anything. I haven’t tested it but it will most likely show up as domain.com in the address bar and will result in an error show to the customer. If chrome wants to strip www as it’s essentially the same domain.com they can submit an RFC and not just decide for everyone. Honestly I hope they start making more stupid decisions like this so ppl move to Firefox so we have more competition.
- baby 8y ago> If the developer does not setup www.domain.com and the user goes there chrome will not “fix” anything Yup, that's on the developers. Hopefully this fix will make it so that it will be easier to setup DNS with just one domain instead of 2. Props to Chrome.
- shodan666 8y agohttps://en.wikipedia.org/wiki/Canada https://fr.wikipedia.org/wiki/Canada
- psychometry 8y agoConsider the different types of records you need to add for those examples if your web host is Heroku or some other cloud provider: https://devcenter.heroku.com/articles/custom-domains https://devcenter.heroku.com/articles/custom-domains
- aylmao 8y agoSomeone mentioned www.citibank.com.sg vs citibank.com.sg in the issue. One of my school's websites: I can't remember what it was and this was before I understood what the difference is, but www worked much better than without iirc. This also applies to m.*, so literally any web-app with a mobile version.
- paulddraper 8y agoSee the issue. http://www.pool.ntp.org/ http://www.pool.ntp.org/ http://pool.ntp.org/ http://pool.ntp.org/ https://www.citibank.com.sg/ https://www.citibank.com.sg/ https://citibank.com.sg/ https://citibank.com.sg/ Plus, this actually removes any www part of the domain. So subdomain.www.example.com shows as subdomain.example.com Why even open that can of worms?
- jsjohnst 8y agoRead the source link. A concrete example (Citibank) is given.
- masswerk 8y agoA) Consider any sharing platforms where unrelated bodies coexist with distinct subdomains under a common root domain (e.g., Blogspot, Tumbler, etc) While "www" is probably a reserved name and mostly not of practical concern, "m" may be a practical issue. B) Consider subdomains for test-purpose like "www.test.www.example.com" (now displayed as "test.example.com", which is actually not even the root of the specific subdomain). C) Users unsure, if they are on the full-featured or a reduced mobile site, when "m" is hidden. D) I may actually want to have a service agnostic default host at the root and subdomains for dedicated servers (like "www", "ftp", "mail", "stun", "voip", etc). Maybe this one just returns a short text message by design, if accessed on port 80. Not every domain is just about the WWW. (Edit: While we may assume that such a server would forward in practice, this may be assuming too much.)
- janeroe 8y ago>> there's a difference between "www.example.com" and "example.com" > Can you link to a site where these two are different? There are 3rd level domains where everyone can register "www.{TLD}". E.g., .com.kg, .net.kg, .org.kg. Look at the www.com.kg. It's also available as www.www.com.kg. Or www.org.kg that's in fact www.www.org.kg. If you display just the last part (com.kg, org.kg), does that mean that you're viewing the root website? Nope, that doesn't. That means that chrome is fucked up.
- alanh 8y agofor ages, my former high school's website did not respond to requests that omitted the www. subdomain :/