Re: Domain name based multihome routing?

2018-06-28 Thread Dale Mahalko
Eh, I gave up on web proxies a couple years back where I work. It is mostly pointless in the age of "SSL for everything" after Snowden spilled the beans on US gov spying of all open traffic. I am not interested in the complexities of MITM certificates that web browsers are going to constantly screa

RE: Domain name based multihome routing?

2018-06-28 Thread Darcy Kevin (FCA)
half Of Grant Taylor via bind-users Sent: Wednesday, June 27, 2018 11:04 PM Cc: bind-users@lists.isc.org Subject: Re: Domain name based multihome routing? On Jun 27, 2018, at 12:27 PM, Darcy Kevin (FCA) wrote: > I’m not convinced DNS has any valuable role to play here. I can see the value

Re: Domain name based multihome routing?

2018-06-27 Thread Grant Taylor via bind-users
On Jun 27, 2018, at 12:27 PM, Darcy Kevin (FCA) wrote: > I’m not convinced DNS has any valuable role to play here. I can see the value for services that have FQDNs that resolve to IP addresses outside of their ASN(s) like Google / YouTube. -- Grant. . . . unix || die smime.p7s Description:

Re: Domain name based multihome routing?

2018-06-27 Thread Grant Taylor via bind-users
On Jun 27, 2018, at 11:59 AM, Dale Mahalko wrote: > Guessing the potential background domains used by Microsoft / Steam, etc and > monitoring bandwidth used by those domains is unfortunately the only option > available. If you can get information on the IP addresses associated with their ASN(s)

Re: Domain name based multihome routing?

2018-06-27 Thread Paul Kosinski
We do something somewhat similar with our LAN. We have a new cable connection and an old DSL connection. The cable is 60x faster, but has a dynamic IP and blocks various ports (esp. 25), so we keep the DSL so we can send email directly etc. Obviously, we don't want to stream video or even do much

RE: Domain name based multihome routing?

2018-06-27 Thread Darcy Kevin (FCA)
, 2018 2:18 PM To: Darcy Kevin (FCA) Cc: bind-users@lists.isc.org Subject: Re: Domain name based multihome routing? On Wed, Jun 27, 2018 at 12:27 PM, Darcy Kevin (FCA) mailto:kevin.da...@fcagroup.com>> wrote: I’m not convinced DNS has any valuable role to play here. Seems like this is a t

Re: Domain name based multihome routing?

2018-06-27 Thread Dale Mahalko
On Wed, Jun 27, 2018 at 12:27 PM, Darcy Kevin (FCA) < kevin.da...@fcagroup.com> wrote: > I’m not convinced DNS has any valuable role to play here. Seems like this > is a traffic-shaping challenge; maybe one of the open source traffic > shaping tools would fit the bill. > A Google search for multi

Re: Domain name based multihome routing?

2018-06-27 Thread Dale Mahalko
Due to the fact that I don't have the ability to program this experiment myself without spending a couple more years to improve my coding skills, could I interest anyone else here to do the programming work? I would prefer someone who is associated with ISC who sounds like they already know the co

RE: Domain name based multihome routing?

2018-06-27 Thread Darcy Kevin (FCA)
. - Kevin From: bind-users On Behalf Of Dale Mahalko Sent: Wednesday, June 27, 2018 1:00 PM To: bind-users@lists.isc.org Subject: Re: Domain name based multihome routing? There is no way to know if this is

Re: Domain name based multihome routing?

2018-06-27 Thread Dale Mahalko
There is no way to know if this is the "right" or "wrong" approach without actually trying it and see what happens. Guessing the potential background domains used by Microsoft / Steam, etc and monitoring bandwidth used by those domains is unfortunately the only option available. It's not like any

Re: Domain name based multihome routing?

2018-06-27 Thread Matus UHLAR - fantomas
On Tue, Jun 26, 2018 at 12:45 PM, Grant Taylor via bind-users < bind-users@lists.isc.org> wrote: Are you saying that you want to dynamically update routes to IPs resolved in real time to specific host / domain names? Such that traffic to specific hosts / domain names is routed over DSL? With th

Re: Domain name based multihome routing?

2018-06-26 Thread Dale Mahalko
On Tue, Jun 26, 2018 at 12:45 PM, Grant Taylor via bind-users < bind-users@lists.isc.org> wrote: > > Are you saying that you want to dynamically update routes to IPs resolved > in real time to specific host / domain names? Such that traffic to > specific hosts / domain names is routed over DSL? W

Re: Domain name based multihome routing?

2018-06-26 Thread Warren Kumari
On Tue, Jun 26, 2018 at 12:45 PM Grant Taylor via bind-users < bind-users@lists.isc.org> wrote: > On 06/25/2018 11:08 PM, Dale Mahalko wrote: > > * The secondary program looks up the domain in a database, which also > > includes the multihome destination for each domain. If a match is found, > > a

Re: Domain name based multihome routing?

2018-06-26 Thread Grant Taylor via bind-users
On 06/25/2018 11:08 PM, Dale Mahalko wrote: * The secondary program looks up the domain in a database, which also includes the multihome destination for each domain. If a match is found, a route is created to that multihome destination. Aliased acceleration domains such as Akamai will be matche

Re: Domain name based multihome routing?

2018-06-26 Thread Dale Mahalko
bly be my only post > here..) > > > > I am looking for a way on Linux to do domain name based multihome > routing. > > > > Essentially every time a domain name lookup request occurs: > > > > * Rather than immediately returning the results to the reque

Re: Domain name based multihome routing?

2018-06-26 Thread Mark Andrews
the result you are after. Mark > On 26 Jun 2018, at 3:08 pm, Dale Mahalko wrote: > > (Hello, I am new to the list. And this may possibly be my only post here..) > > I am looking for a way on Linux to do domain name based multihome routing. > > Essentially every time a domai

Domain name based multihome routing?

2018-06-25 Thread Dale Mahalko
(Hello, I am new to the list. And this may possibly be my only post here..) I am looking for a way on Linux to do domain name based multihome routing. Essentially every time a domain name lookup request occurs: * Rather than immediately returning the results to the requesting program, instead