Closed brandonhilkert closed 5 years ago
Ah, my bad, just found it in the options
attr of the transaction. Thanks again!
I'd still be interested in your thoughts on 2 :)
RubyDNS was originally the entire stack. It split into async
+ async-dns
+ rubydns
. RubyDNS is old, and it only really exists for compatibility or when you have a specific need for a DSL.
So, for 2, I'd suggest just building directly on top of async-dns
.
Also, if you are building a commercial project and it's successful, please consider supporting the continued maintenance and development of async
and async-dns
:)
Hey thanks so much for these gems! I assumed I'd have to deal with another language to put up a service like this.
We're looking to do a filter service based on request IP. With a downloaded ruleset from our services, look up the rules for that request IP, determine if it should be allowed, if allowed passthrough to a forwarding bind server, if not, serve backed an IP for a blocked page.
Two questions:
rubydns
, do you recommend using this dependency to build something like the above, or usingrubydns
as a starting point? The rules inrubydns
didn't seem to match our requirements.