From: botp <botpena@...>
Date: 2013-05-23T12:42:24+09:00
Subject: Re: [ANN] RubyDNS - asynchronous DNS client and server for Ruby.

--bcaec548a13d5792d004dd5a789f
Content-Type: text/plain; charset=UTF-8

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

--bcaec548a13d5792d004dd5a789f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote">On Thu, May 23, 2013 at 4:0=
8 AM, Panagiotis Atmatzidis <span dir=3D"ltr">&lt;<a href=3D"mailto:atma@co=
nvalesco.org" target=3D"_blank">atma@convalesco.org</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">I&#39;m a bit offtopic really but, I th=
ink the &#39;correct&#39; way to do this would be to monitor the DNS reques=
ts issued either by RubyDNS or any other DNS server/client at port UDP:53 w=
ith a firewall (pf, iptables, ipfw, etc) or tcpdump grab the values that ar=
e of interest from their logs and then run a ruby (or pythong, or whatever)=
 script that collects the info you want.<div>
<div><div><br></div></div></div></div></blockquote><div><br></div><div>in a=
 way, yes. =C2=A0But in this case i do it =C2=A0mainly for 2 reasons:</div>=
<div>1 defense in-depth. protection at network level + protection at applic=
ation level=C2=A0</div>
<div>2 split dns=C2=A0</div><div><br></div><div>now, as to why rubydns inte=
rest me:</div><div>1 rubydns would shine on environments w heterogeneous dn=
s setup, some have bind, djbdns, etc... =C2=A0using ruby(dns), i wont have =
problems reading their differing databases..</div>
<div>2 adhoc dns.. =C2=A0eg, i can just run a temp rubydns, while i fix the=
ir problematic bind dns...</div><div>3 scale and economics. =C2=A0install r=
uby &amp; deploy.=C2=A0</div><div>4 collaboration. =C2=A0 my ruby/rails/sin=
atra apps can now communicate seamlessly &amp; natively with our dns server=
s...</div>
<div><br></div><div>kind regards</div><div>-botp</div><div><br></div><div><=
br></div></div></div>

--bcaec548a13d5792d004dd5a789f--