1. 7

  2. 3

    I’m not clear what advantages, if any, exist here vs. dnsmasq. It may be that there aren’t any beyond “it’s lighter-weight than dnsmasq due to lacking a DHCP server,” or even just that the author wanted to scratch and itch, both of which are fine, but I’m curious.

    1. 4

      I thought the most interesting part was actually the resolver(5) system in OSX, which lets you delegate a TLD or whatever to your development environment, eg, .dev.

      Using devdns + resolver(5) is a pretty low configuration method to get a working DNS for your own development environment and point it to a VM on your mac – and this lets you have things like ${customerName}.mything.dev on your local VM work without a ton of /etc/hosts entries.

    2. 2

      I built a similar tool called Pult that also handles assigning ports to local servers and proxying them from port 80 on localhost.