Now I'm kind of curious, what is your expertise and what are you doing with
DNS?


On 23 May 2013 15:42, botp <botpena / gmail.com> wrote:

>
> On Thu, May 23, 2013 at 4:08 AM, Panagiotis Atmatzidis <
> atma / convalesco.org> wrote:
>
>> I'm a bit offtopic really but, I think the 'correct' way to do this would
>> be to monitor the DNS requests issued either by RubyDNS or any other DNS
>> server/client at port UDP:53 with a firewall (pf, iptables, ipfw, etc) or
>> tcpdump grab the values that are of interest from their logs and then run a
>> ruby (or pythong, or whatever) script that collects the info you want.
>>
>>
> in a way, yes.  But in this case i do it  mainly for 2 reasons:
> 1 defense in-depth. protection at network level + protection at
> application level
> 2 split dns
>
> now, as to why rubydns interest me:
> 1 rubydns would shine on environments w heterogeneous dns setup, some have
> bind, djbdns, etc...  using ruby(dns), i wont have problems reading their
> differing databases..
> 2 adhoc dns..  eg, i can just run a temp rubydns, while i fix their
> problematic bind dns...
> 3 scale and economics.  install ruby & deploy.
> 4 collaboration.   my ruby/rails/sinatra apps can now communicate
> seamlessly & natively with our dns servers...
>
> kind regards
> -botp
>
>
>