On 6/13/07, Adrian von Bidder <[EMAIL PROTECTED]> wrote: > I don't see what we're gaining here. www.pool.ntp.org has always been the > documented location for the web page. Your proposal doesn't (and can't) > stop people who just type pool.ntp.org. even worse: pool-project.ntp.org > is not logical, while some people might go to www... if the pool.ntp.org > addres timeouts or refuses connection. (much rarer if it just returns a > different web page.)
I was thinking that the main reason people try to connect to http://pool.ntp.org on port 80 is because of the fact that the main project web page is http://www.pool.ntp.org. People often leave out the www when typing in web addresses. If the main project page was in a different sub-domain, or better yet a different 2nd-level domain, the situation would be different. If the project management pages were at http://www.ntp-pool.org, or some other separate domain, why would anyone ever type in http://pool.ntp.org? Whatever the actual domain name is doesn't matter, so long as it is not in the *.pool.ntp.org hierarchy. At this pool.ntp.org can't be changed as the hostname for the global NTP server pool, but the DNS name for the project management web pages can be changed to avoid this confusion. Splitting "infrastructure" DNS names from user-oriented names is done quite a bit, and is probably a good idea. For example, Google uses the smtp.google.com sub-domain for its MTA pool, and mail.google.com for their Gmail web server pool. There's little chance of someone trying to connect to a Google MTA with a web browser because the name spaces are different. Wouldn't it be horrible if http://www.mail.google.com were the web mail service, but http://mail.google.com timed out because that was actually a pool of MTAs? -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
