48

Like the title says, running os x 10.10.1. if i have an entry in my hosts file and do a dig or nslookup it still shows a different IP than what is in my hosts file even after trying to flush various caches.

I have tried the following..

  1. flush mdns and udns caches by running:
    1. sudo discoveryutil mdnsflushcache;
    2. sudo discoveryutil udnsflushcaches;
  2. flush cache using dscacheutil -flushcache
  3. reload the discoveryd.plist file
    1. sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
    2. sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

my hosts file looks like this..

% cat /private/etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##

127.0.0.1   localhost
255.255.255.255 broadcasthost
::1             localhost
fe80::1%lo0 localhost
166.78.60.102   admin.devsite1.com
bmike
  • 226,393
  • 78
  • 398
  • 871
NDBoost
  • 569
  • 1
  • 4
  • 10
  • 3
    It seems Yosemite isn't using hosts in the same way as before; it doesn't flush caches the same way either, & mDNS has taken a back seat - This has a whole bunch of chatter on the subject - http://forums.macrumors.com/showthread.php?t=1741422 *Edit* ahh... I guess you've already got as far as http://azchipka.thechipkahouse.com/dns-overrides-yosemite-10-10-etchosts/10473/ – Tetsujin Nov 25 '14 at 20:05
  • thanks, yeah I read that already.. if this is how os x is going to be.. its crummy :\ – NDBoost Nov 25 '14 at 20:07
  • 1
    I'm glad I don't have to rely on hosts on Mac, tbh; I tend to always be playing in Win when I need to do that - though that's not the only thing keeping me away from Yosemite right now :( – Tetsujin Nov 25 '14 at 20:08
  • Yeah my rmbp is the primary dev machine that I use for web development/sysadmin unfortunately and I need to get this figured out otherwise i'll be rolling back to mavericks. – NDBoost Nov 25 '14 at 20:09
  • Others may want to just disable ipv6 on their workstations, I found this which explains the key: https://www.technipages.com/how-to-disable-ipv6-in-macos-sierra - However, even after disabling ipv6 on my nic, the problem persisted. – James T Snell Mar 10 '17 at 20:50

9 Answers9

70

/private/etc/hosts seems to be working normally for me in Yosemite (version 10.10.1). It's not necessary to flush the cache or reset discoveryd (the DNS resolver in Yosemite); sudo fs_usage | grep private/etc/hosts shows discoveryd reading the file immediately after I save changes to it.

[Update: discoveryd was only used in OS X versions 10.10.0 - 10.10.3. In both earlier and later versions, mDNSResponder provides the same function... and also immediately notices changes in /etc/hosts.]

However, dig, nslookup, and host will not see entries in it because they bypass the system's resolver and do raw DNS lookups. They've always done this, so this is not new in Yosemite. The "official" way to do a lookup through the system resolver in OS X is to use dscacheutil:

dscacheutil -q host -a name www.example.com

...but since that's painfully verbose, I tend to just use ping instead (and then look at the first line, where it lists what IP it's pinging). Starting in 10.9, you can also use Network Utility's Lookup tab (before that it used dig, and therefore bypassed the system lookup policy).

BTW, please pay no attention to the macrumors thread that Tetsujin linked; it's full of people who don't quite know what they're doing and are misunderstanding the results of their own mistakes.

Gordon Davisson
  • 32,089
  • 6
  • 67
  • 90
  • 1
    thanks Gordon, yeah I realized after I posted this that `dig`, `nslookup`, and `host` don't use local dns resolution. That being said `/etc/hosts` works as expected.. – NDBoost Dec 03 '14 at 17:19
  • If I update my `/etc/hosts` file or my `/private/etc/hosts` file, then it doesn't reflect at all with `dscacheutil -q host -a name www.example.com` or any other command.. – Trip Sep 30 '15 at 14:51
  • 4
    @Trip make sure the entries you added are properly formatted: IP address followed by a space or tab, followed by the name, then a linefeed at the end of the line. Try printing the hosts file with `cat -vet /etc/hosts` to make normally invisible characters visible. Each line should look like "127.0.0.1^Inetsecuritybureau.com$" (the "^I" is a tab, and the "$" is the linefeed) or "127.0.0.1 netsecuritybureau.com$". If you see a "^M" (carriage return) just before the "$", you have DOS/Windows formatted text and you need to remove the carriage return(s). – Gordon Davisson Sep 30 '15 at 16:24
  • Ah wow thanks so much for the help. I followed your lead on ensuring it's a tab or space. My line reads exactly : `M127.0.0.1^Iyoutube.com^M^M` , I then performed `dscacheutil -flushcache; sudo killall -HUP mDNSResponder` and when navigating to youtube.com it still brings up youtube and not localhost. – Trip Sep 30 '15 at 16:33
  • @Trip There are a number of ways of cleaning up invisible characters like those at the command line, but I'll recommend the GUI editor [TextWrangler](http://www.barebones.com/products/textwrangler/) -- use View menu > Text Display > Show Invisibles to see (and edit out) things like those carriage returns. Also, it's free, and has options to show/open invisible files and folders (like /etc), and to use admin rights to edit system files. – Gordon Davisson Oct 01 '15 at 23:46
  • We are experiencing this issues since Sierra (we = several machines). Everytime we enter a certain network with assigned DNS via router hosts file is ignored. Simple solution: Switch DNS provider on router. But this is necessary every morning :-( WTF? After this it resolves again against local hosts file. – Strinder Feb 07 '17 at 12:04
21

I have discovered another wrinkle with this issue.

In order to fix the problem I was having, I had to ADD IPv6 style hosts file entries.

It seems that Safari will overlook IPv4 entries IF you have an IPv6 network configuration setup.

You must add duplicate entries that resolve to IPv6 localhost address in /etc/hosts.

IPv4 entry 127.68.56.101 facebook.com

e.g. IPv6 entry fe80::1%lo0 facebook.com

etc.

mmmmmm
  • 28,660
  • 17
  • 84
  • 140
JB Smith
  • 211
  • 1
  • 2
1

My hosts file kept on being ignored after I edited in text edit. I tried several ways to fix the line endings, added IPv6 entries to the existing IPv4 entries with no success following JB Smiths answer above. I suspect his answer would work if my company supports IPv6 which I found out after my attempts.

The only solution that worked for me is using this free GUI plugin to edit hosts file.

https://github.com/specialunderwear/Hosts.prefpane/blob/master/README.mdown

Community
  • 1
Danger14
  • 1,939
  • 2
  • 15
  • 13
1

I found this article because Yosemite 10.10.5 was not picking up my hosts file changes, and nothing I could do was fixing it. (I rebooted, tried flushing caches, followed every bit of advice I could find on the internet etc etc).

The answer was so simple it is embarrassing, actually, but I thought I'd share. I used textedit to edit the hosts file, and it took the liberty of saving the file as hosts.txt. Normally I would notice something like this, but I am using a fresh install of Yosemite and hadn't yet turned on "show all file extensions" so it didn't look like the file name had changed when I viewed it on my desktop.

So it's kinda obvious, and most people reading this post have probably already done this, but be sure to check that your hosts file is actually there and hasn't been replaced by hosts.txt.

To turn on displaying filename extensions go to Finder > Preferences > Show all filename extensions

To stop TextEdit from adding .txt extension to files, open a file in Text edit and choose File > Save As (If you don't see the Save As menu item, hold down the option key after you click File, and Save As should appear in the menu). Look for the option If no extension is provided, use ".txt" and deselect it.

sandra
  • 11
  • 1
0

I believe Apple will recognize this as a bug (I submitted one today). I did notice that new entries in /etc/hosts are picked up but, changes to existing entries are ignored. So.... changing an entries' hostname (e.g. web1 to web1a) provided a workaround for me.

OLD /etc/hosts entry: 54.173.164.18 web1

NEW /etc/hosts entry: 54.174.161.12 web1a

user3439894
  • 55,813
  • 9
  • 101
  • 125
Mark
  • 1
  • 1
0

In my case I'd set up a .ssh/config

#Host *.ourdemo.ca
  User jumpy
  ProxyCommand ssh ourjumpbox.ca -W %h:%p
Martin Cleaver
  • 203
  • 1
  • 4
  • Would you mind explaining what the config file does and how this is related to the question? – klanomath Apr 21 '16 at 20:47
  • 1
    The question was why was an entry in a local /etc/hosts file being ignored. In my case, it was being ignored because I'd instructed to tunnel all traffic to a set of machines (*.ourdemo.ca) through a proxy box (ourjumpbox.ca). SSH obediently proxied the connection, such that it ended up being the proxy's /etc/hosts file being used to resolved the address rather than my local /etc/hosts file. – Martin Cleaver May 22 '16 at 00:31
0

I had a very similar issue in which i received via mail two rows to be added to my /etc/hosts

The domain contained a - like my-domain.com

The problem turned out to be the sender's email client - no matter to say, MS Outlook - that converted the ascii - in the long - character that Microsoft loves so much to use its embedded automatic correction to substitute the - with their -.

The hosts file did look perfect and it was hard to find this issue. When i deleted the rows and wrote it back manually, they started working.

It was so difficult to understand this, that i went deeply inside why the MacOS client should ignore the hosts file and skip directly to name resolution.

John N
  • 1,448
  • 4
  • 13
  • 22
Marco
  • 101
  • 3
0

Just had this problem. It was caused by making copy/paste from hipchat instead of writing the address.

The copy process added some bad characters instead of spaces and caused the problem.

Rewriting the row solved the problem.

Tata
  • 281
  • 3
  • 6
0

I'm using the app SelfControl (actually on macOS mojave 10.14.4) for quite a while now and figured to check how SelfControl does it's entries... they look like this:

0.0.0.0 xyz.com
:: xyz.com
0.0.0.0 www.xyz.com
:: www.xyz.com

based on this I changed everything to my localhost, so 

127.0.0.1
::1

works.

needlol
  • 114
  • 8
  • I'm not sure how this answers the question at all. It seems like just some random observation, unrelated to the question. – Tetsujin May 09 '19 at 11:34
  • 1
    Can you add some details on where exactly you changed what, and how it relates to the question? – nohillside May 09 '19 at 11:54
  • The question was why the hosts file is being ignored since 10.10.1... I was in the same situation that manual entries were ignored but entries made via the app SelfControl, were working as intended. What was missing with my prior entries, was the second part, domains with "www.". Wasn't able to figure out what else was wrong with my entries, since all was working fine before 10.10.1. – needlol May 16 '19 at 10:42