Closed pda closed 8 years ago
Hi, in response to this, I've updated RubyDNS with one final development version, 0.8.0, can you please test this. Once I've confirmed that everything is working, I'll make this the official 1.0.0 release.
@ioquatix I have the 0.6 branch with RubyDNS 0.8.0 running locally since almost a week now, looking good to me. Just updated to 0.8.4, also no issues so far.
@fnordfish THANKS so much, I really appreciate the feedback.
The only major change is that in run_server
I added trap(:INT) { EventMachine::stop }
so that if you press Ctrl-C the whole thing shuts down nicely.
The other thing I've been working on is performance evaluation and cutting out anything which is causing performance problems. In the latest unit test, both the resolver and the server is tested. The asynchronous EventMachine is quite a bit faster than the built in system resolver when dealing with multiple names (to be expected I guess), and the server code is generally on bar with bind9, but under heavy loads only up to 3 times slower overall - I think this is due to some issues in EventMachine so I'm currently investigating that, but I feel like if I get a few more good reports from users we are pretty close to a 1.0.0 release.
Again, thanks SO much for your testing.
@ioquatix Your are more than welcome! I assume, that most ppl. using this plugin for vagrant won't need a bind9-like performance ;)
Again, no issues since 9 days (fb4b90209111acdfebfe768602d63dc7bd655a2b) running 0.8.4
Missed the rubydns 1.0 release. vagrant-dns 1.0.0 has been released with rubydns 1.0.2 Thanks for your patience.
As people are using this out in the wild, it'd be great to tag a v1.0.0 release, and follow semver from there.
See also: https://github.com/ioquatix/rubydns/issues/28