Yeah, but it's not an exact science, any way you slice it.
I just did a quick crunch of yesterday's data from our web proxy logs, and
accesses of URIs based on the FQDN "b.scorecardresearch.com" (a banner ad site,
I believe) had over 570 different combinations of website content categories,
depending on URI. One FQDN, 570 different possible ways one might want to
direct the traffic. DNS-based approaches simply may not have the granularity
necessary to get the job done.
Speaking of web proxies, that should probably be the *first* thing that gets
put into place, if the goal is minimize "disfavored" web traffic from
traversing expensive WAN connections.
- Kevin
-----Original Message-----
From: bind-users <bind-users-boun...@lists.isc.org> On Behalf 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) <kevin.da...@fcagroup.com>
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
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
