Curious! (wkipedia random page look):
Comodo -> 8.26.56.26 && 8.20.247.20
as-path for those both:
174 23393 23393 16589
6762 3257 23393 23393 16589
$ whois AS16589
No match found for a 16589.
(https://bgp.he.net/AS16589#_whois)
So, sending your DNS queries into what sure looks like hijacked
Oh, Bill. If you’d use Wikipedia to check out Wikipedia, you’d be allergic too!
:)
https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_is_not_a_reliable_source
-mel
On Feb 1, 2021, at 3:32 PM, Bill Woodcock wrote:
Are all y’all allergic to Wikipedia or something?
> On Feb 1, 2021, at 5:26 PM, Kevin McCormick wrote:
>
> Nearly all of those seem to error out.
>
> Is that a wishful thinking list?
Those that do answer to anyone who asks are flagged "recursion-yes,” but I
don’t know how often it’s updated.
—Chris
On Feb 2, 2021, at 00:34, Douglas Fischer wrote:
Or even know if already there is a solution to that and I'm trying to invent
the wheel.
Many flow telemetry export implementations on routers/layer3 switches report
both passed & dropped traffic on a continuous basis for DDoS
Are all y’all allergic to Wikipedia or something?
https://en.wikipedia.org/wiki/Public_recursive_name_server
-Bill
signature.asc
Description: Message signed with OpenPGP
Nearly all of those seem to error out.
Is that a wishful thinking list?
Thank you,
Kevin McCormick
-Original Message-
From: NANOG On Behalf Of Chris
Boyd
Sent: Monday, February 1, 2021 4:17 PM
To: North American Network Operators' Group
Subject: Re: public open resolver list?
>
> On Feb 1, 2021, at 12:19 PM, Nick Hilliard wrote:
>
> Randy Bush wrote on 01/02/2021 18:16:
>> is there a list of public resolvers? e.g. 1.1.1.1, 4.4.4.4, 8.8.8.8,
>> etc.?
>
> https://public-dns.info/
There’s also a list of interesting resolvers at
On 10:49 01/02, Randy Bush wrote:
> >> is there a list of public resolvers? e.g. 1.1.1.1, 4.4.4.4, 8.8.8.8,
> >> etc.?
> >
> > https://public-dns.info/
>
> interesting, but probably too broad.
>
> but i suspect my question was too broad.
>
> >> we have a measurement set which contains
>> is there a list of public resolvers? e.g. 1.1.1.1, 4.4.4.4, 8.8.8.8,
>> etc.?
>
> https://public-dns.info/
interesting, but probably too broad.
but i suspect my question was too broad.
>> we have a measurement set which contains resolvers, some of which we
>> suspect are intentionally
There are several good articles about the different ones out there and the
level of filtering and response they can offer. I personally have been happy
with Quad9's free DNS server (9.9.9.9) and the basic anti-bad stuff filtering
it does. You get no reporting on what it blocks, but there are
Randy Bush wrote on 01/02/2021 18:16:
is there a list of public resolvers? e.g. 1.1.1.1, 4.4.4.4, 8.8.8.8,
etc.?
https://public-dns.info/
?
Nick
is there a list of public resolvers? e.g. 1.1.1.1, 4.4.4.4, 8.8.8.8,
etc.?
we have a measurement set which contains a list of resolvers, some of
which we suspect are intentionally open, some unintentionally open,
and some not open. we are trying to filter that first set, the
intentionally open.
It went down again today and last Sunday.
And yes, we can see 206.72.210.143 with heavy packet loss too. They said
that they will send us a RFO last Friday but I haven't got one.
On Tue, Feb 2, 2021 at 1:59 AM Seth Mattinen wrote:
> On 1/26/21 3:51 AM, Siyuan Miao wrote:
> > Does anybody know
On 1/26/21 3:51 AM, Siyuan Miao wrote:
Does anybody know if there's an alternative to Any2 Los Angeles
with predictable uptime and enough members in LA?
It's the second outage this month and we've observed at least 7 outages
in the past year and we didn't even receive any maintenance notice
I think most here know (way better than me) the concepts of DDoS, anomaly
detection, and reactions.
Some of the reactions that can be implemented to reduce the impact of an
attack are Remote-Triggered BlackHole and FlowSpec Filtering.
In theory, using FlowSpec would be possible to de source the
Rod,
I received the information you requested of the NANOG listserv from Telxius
- Ashburn DC2 to CLS Sopelana RTD = 69.5ms
- Ashburn DC2 to Derio POP = 71ms
Hope this helps!
-Ilissa
On Mon, Feb 1, 2021 at 9:22 AM Rod Beck
wrote:
> Off list, please. Anyone know the RTD of this
*The latest technology, all in one space*
Be sure to visit the NANOG 81 Virtual Expo throughout the conference to
learn about the latest technologies, and connect with reps from North
American companies and beyond! Plus, you'll have the chance to win a
variety of swag + prizes, and pick up clues
*The latest technology, all in one space*
Be sure to visit the NANOG 81 Virtual Expo throughout the conference to
learn about the latest technologies, and connect with reps from North
American companies and beyond! Plus, you'll have the chance to win a
variety of swag + prizes, and pick up clues
I think that report is a summary of the thinking that led to the new higher
count cables. In fact, those researchers work for the companies that laid those
cables.
The new cables are based on the ideas outlined in that paper? spacing regen
farther apart, putting fewer waves on each fiber pair
On 2/1/21 12:30, Rod Beck wrote:
Here is the intellectual foundation or underpinnings of the new deep
sea design which are enabling fiber pair counts as high as 24.
I think the engineers might enjoy this.
https://ieeexplore.ieee.org/document/8369356
Off list, please. Anyone know the RTD of this cable from its Ashburn POP to its
Bilboa cable landing station. A 2018 press release brags it is one of the
lowest latency Trans-Atlantic cables.
Regards,
Roderick.
Roderick Beck
VP of Business Development
United Cable Company
Here is the intellectual foundation or underpinnings of the new deep sea
design which are enabling fiber pair counts as high as 24.
I think the engineers might enjoy this.
https://ieeexplore.ieee.org/document/8369356
This one at Aargauerstasse 10 in Zurich is operated by the incumbent Swisscom,
mainly for their own purpose. It‘s called «Zurich Herdern» with LEX code
790ZHH, despite it‘s not a LEX in the classical sense.
There is a similar one in another area of the city called «Zurich Binz» with
the code
23 matches
Mail list logo
