Currently Being ModeratedOct 25, 2011 6:58 AM (in response to rs2122)
It's broken for me too. Worked in Snow Leopard.
If you run this in termina: scutil --dns
(note double dashes)
... you will see that the resolve order is set to check the DNS server first, so I'm guessing that's what's happening, if there's a hit, it will take you there, otherwise move on to resolver #2.
Maybe this will work for you instead:
I tried it, but it didn't work for me, maybe it will for you.
Only thing left is to either wait for Apple to fix it (but I'm afraid this is on purpose, and not a bug), or install DNSMasq and run your own DNS server, as described here: http://www.justincarmony.com/blog/2011/07/27/mac-os-x-lion-etc-hosts-bugs-and-dn s-resolution/
Currently Being ModeratedOct 25, 2011 7:07 AM (in response to rs2122)
search domain : lan
nameserver : 18.104.22.168
nameserver : 22.214.171.124
domain : local
options : mdns
timeout : 5
order : 300000
Local is Resolver #2.
I tried the dscl option but it also didn't work for me.
Installing DNSMasq is a bit to much for me. There are a lot of developers that use the hosts file.
I really hope Apple will provide a solution for this bug. (it's is a bug not a feature!)
Currently Being ModeratedOct 25, 2011 7:10 AM (in response to rs2122)
Installing DNSMasq is also a bit too much for me. Luckily I don't rely too much on the hosts file so I can afford to wait it out a little longer until hopefully a fix or workaround happens.
Currently Being ModeratedOct 25, 2011 9:28 AM (in response to rs2122)
Solved!! I can't believe how easy it actually was, it was just a matter of unix line endings, apparently. Hopefully it will work for you too: http://techpatio.com/2011/guides-how-to/fixed-mac-osx-lion-etc-hosts-bugs-dns