daguej/node-dns — comment on commit 0783e95d823887af1d3de95ae46d949f6e477531
File:  line 0
By tjfontaine:

This speaks to a broader issue I want to handle, I want consumers to be able to manage nameservers on their own, external to what the platform provides. I just haven't come up with an interface that I liked. It should be a mechanism to add/remove {server:,port:} such that when servers are available they set name_server_ready and checkReady so that the client portion is notified it can send queued requests.

The reason parseResolve doesn't take a filename, and parseHosts does is because I knew the logic could probably be mostly reused on all platforms. On the contrary I knew parsing a resolv.conf wasn't going to be possible on all platforms so I planned on having a separate function specifically for windows, I hadn't investigated what to do in that case. So anyway, adding the switch in parseResolve is not the right solution but adding a new function that's only called from the original switch is what I would prefer.

I want this to work on windows, and I'm fine with bootstrapping to the point where it doesn't except on start.