[181602] in North American Network Operators' Group
Re: CDNs for carriers
daemon@ATHENA.MIT.EDU (Blake Hudson)
Mon Jun 29 10:46:08 2015
X-Original-To: nanog@nanog.org
Date: Mon, 29 Jun 2015 09:46:03 -0500
From: Blake Hudson <blake@ispn.net>
To: nanog@nanog.org
In-Reply-To: <CAL9jLab6s6O3VWxYhh_KQK9bDuOMAB4Y2ROZjuahAb92Hwb4sw@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
Christopher Morrow wrote on 6/29/2015 9:25 AM:
> On Mon, Jun 29, 2015 at 10:21 AM, Jared Mauch <jared@puck.nether.net> wrote:
>> This being said, there is not a single solution to everything. Chris mentioned using DNS, which is a nice method assuming you see all the queries within your traffic cone.
>
> sorry, I meant that you could just look at the reverse dns for some of
> the higher traffic sources/destinations... you can ALSO look at your
> recursive dns servers to see what folk are looking up 'often'... which
> is a third tool to use. (presuming you see all/most/representative-set
> of your customers, yes)
For hosts with no (or meaningless) reverse DNS, I've found that browsing
to the IP in question via HTTPs will often provide an SSL certificate
with lots of useful information.
--Blake
