On 28 Oct 2013, at 07:36, William H. Magill <[email protected]> wrote: > > On Oct 26, 2013, at 4:56 PM, Jerry Levan <[email protected]> wrote: >> >> Does Safari do something wonky with name to ip lookups? > > Easy example -- type "apple.com" and you go to "www.apple.com" -- instead of > failing, as it should. > (And these situations are NOT my ISP being "helpful" -- that brings up a > separate page of "suggestions.”)
That’s an unfortunate example! 8:23 ~ ➤ host apple.com apple.com has address 17.172.224.47 apple.com has address 17.178.96.59 apple.com has address 17.149.160.49 apple.com mail is handled by 10 mail-in6.apple.com. apple.com mail is handled by 20 mail-in24.apple.com. [etc] I know browsers like Netscape were appending “.com” to names that didn’t resolve, and then prepending “www.” to things that still didn’t resolve. So you could type in “apple” and it would try to resolve it, then stick “.com” on the end because there was no TLD, attempt to resolve that and if that failed, stick “www.” on the front. That’s from the days when OS X 10 was brand new and Bondi iMacs were still a thing. As for Mavericks blowing away stuff that you’ve installed, it’s Unix Administration 101 that you don’t fiddle with vendor directories: all the stuff you install locally should go in /usr/local, /opt/local or somewhere else that isn’t /bin, /sbin, /lib, etc. Sorry for being so brief. Alex _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
