M Graff wrote: > The slight variance between www.pool.ntp.org and pool.ntp.org is > dangerous because if www times out, many browsers just try it without > the www part, so the user doesn't even have a chance to be stupid.
My Firefox add "www" to the hostname, if the host does not exist without "www", but I have never tried it in the opposite way. Which browser does have that behavior? I just did a small test here, where i added "somedomain.invalid" to my hosts file, and pointed the IP address to my own server which answers with a default page on all hostnames. I didn't get any response when browsing "www.somedomain.invalid". If I switched it around, having "www.somedomain.invalid" in my hosts file and browsed "somedomain.invalid", Firefox automatically added "www" to the URL, since it found no record for "somedomain.invalid". My default page from the webserver showed up then. Another thing about this... Firefox only have this behavior if it can't find a DNS record for the 2nd level domain. I tried to make "somedomain.invalid" point to a IP of a server with no webserver running, and browsed "somedomain.invalid" while "www.somedomain.invalid" still pointed to my webserver, and then Firefox didn't try to connect to "www.somedomain.invalid". From a pool perspective we can't use this for anything, since we always have a record for "pool.ntp.org". I hope that cleared up a bit, if it wasn't too confusing. Kind regards Jeppe Toustrup _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
