Local web development with POW

Comments

4 comments

  • Avatar
    jedisct1

    Check that a file called "dev" is present in /etc/resolver/ or see the resolver(5) man page. It should contain something like:

    nameserver 127.0.0.1

    Queries sent to .dev (or anything listed in /etc/resolver) shouldn't hit OpenDNS or any other external resolver.

    If you're using the dnscrypt user interface for OSX, you can also add "dev" to the list of exceptions. It will automatically create the file in /etc/resolver/ for you.

    Keep on writing Ruby code!

    0
    Comment actions Permalink
  • Avatar
    tomrossi7

    Yes, the "dev" file contains:

    # Lovingly generated by Pow
    nameserver 127.0.0.1

    I believe it is an issue related to Google Chrome, but I was hoping that I could fix it through OpenDNS disabling the website-unavailable.

    https://code.google.com/p/chromium/issues/detail?id=82772

     

    0
    Comment actions Permalink
  • Avatar
    jedisct1

    Sucks. Looks like Chrome bypasses the OSX resolver mechanism.

    An easy workaround is to run a local DNS cache on your laptop. I would highly recommend Unbound (it's in Homebrew).

    In addition to acting as a caching resolver, Unbound can directly serve local zones (see local-zone and local-data). So you can use 127.0.0.1 as a DNS resolver, and override anything in .dev or even with the real domain name you will be using.

    The built-in DNS cache in OSX is crap (way less in Mavericks, though), so having a local resolver is often a good idea no matter what.

    0
    Comment actions Permalink
  • Avatar
    jedisct1

    As a side note, even if you forward everything to OpenDNS, Unbound let you override this for some specific domains. So that you can, for instance, resolve Akamai domains locally or using your ISP resolver, so that the iTunes Store is not dead slow. Yet another good reason to run a local cache.

    0
    Comment actions Permalink

Please sign in to leave a comment.