Closed kjagiello closed 12 years ago
Thanks! I have a question though... focus.py reads in the nameservers from /etc/resolv.conf, so that it knows which one to forward certain requests to. If Mac doesn't use resolv.conf, can you think of a good way for focus to know about the other nameservers?
It seems that Mac OS X uses /etc/resolv.conf to store the address of the nameserver. I'm far away from my Mac right now, but I will check that for you tommorow if nobody helps you with that before me.
Krzysztof-Jagiellos-MacBook:~ krzysztofjagiello$ cat /etc/resolv.conf
#
# Mac OS X Notice
#
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
#
# This file is automatically generated.
#
domain adm.ovansiljan.net
nameserver 192.168.1.12
nameserver 192.168.1.13
perfect, ok it should work fine then
The problem isn't focus.py being able to use /etc/resolv.conf. It is that the web browser (eg Chrome) does not resolve domains using resolv.conf ("most processes" as mentioned in the header), so even if 127.0.0.1 is in resolv.conf, the domain name requests made by the web browser never route to 127.0.0.1 (unless it is added to the DNS servers in the Mac system preferences) and therefore never to focus.py.
Moving the discussion to issue #8
Simple instructions how to configure DNS on Mac OS X to work with Focus.