lhc> How much did it cost? :-)
valdis> I'm willing to guess US$6digits/mo. 5 digits if you qualified for
valdis> the quantity discount. :)
We used to charge $2500 install and $2500/month for a T1 with agreement
to not share or resell. It was something like double that if you wanted
to resell? We
On Tue, 30 Apr 2019 22:12:12 -0700, Large Hadron Collider said:
> How much did it cost? :-)
I'm willing to guess US$6digits/mo. 5 digits if you qualified for
the quantity discount. :)
pgpgvdL3ozP2_.pgp
Description: PGP signature
How much did it cost? :-)
On 19-04-30 08 h 38, Bryan Holloway wrote:
On 4/29/19 7:21 PM, Valdis Klētnieks wrote:
On Mon, 29 Apr 2019 16:16:06 -0500, Bryan Holloway said:
I still see references to UUNet in some reverse PTRs.
So, uh, yeah.
I wonder what year we'll get to a point where less
Hi,
I am aware that some PTR records are wrong. Can you please name the
half dozen ISPs / suffixes so I can take a look at those in the data.
In theory the code should score suffixes which have out of date
records poorly. For suffixes that don't score poorly but have errors,
there are other
Automation isn’t even that hard - just outsource (e.g. 6Connect).
I get why some things stagnate & collect kruft. But it is actually EASIER, and
probably cheaper (including people time), to have a 3rd party “just do it” when
it comes to things like DNS & IPAM.
Then again, if everyone ran
On 4/29/19 7:21 PM, Valdis Klētnieks wrote:
On Mon, 29 Apr 2019 16:16:06 -0500, Bryan Holloway said:
I still see references to UUNet in some reverse PTRs.
So, uh, yeah.
I wonder what year we'll get to a point where less than half of NANOG's
membership was around when UUNet was. We're
On 4/30/19 7:12 AM, Jared Mauch wrote:
While at NTT and at Akamai we have managed to publish sane PTR records
and make the forward work as well. You need to automate it by pulling
from your router configuration database and publish to your DNS
database. If you are still doing either by hand
While at NTT and at Akamai we have managed to publish sane PTR records and make
the forward work as well. You need to automate it by pulling from your router
configuration database and publish to your DNS database. If you are still doing
either by hand then it’s time to make the switch ASAP.
On 30/4/19 10:38 am, Chris Adams wrote:
> I still refer to ASes by companies that haven't existed in ages... 701
> is UUNet, 3561 is MCI, 1 is BBN, etc. :) I don't handle name changes
> well (I also refer to one of the main roads where I live by a name it
> hasn't had in close to 20 years).
This
lg.hadron> And 666 is Nero Caesar :-)
surfer> It's the US Army.
Same same... :)
--- large.hadron.colli...@gmx.com wrote:
And 666 is Nero Caesar :-)
--
It's the US Army.
scott
And 666 is Nero Caesar :-)
On 19-04-29 17 h 38, Chris Adams wrote:
Once upon a time, Valdis Klētnieks said:
I wonder what year we'll get to a point where less than half of NANOG's
membership was around when UUNet was. We're probably there already.
And likely coming up on when less than half
I legit guffawed.
On 19-04-29 13 h 13, Eric Kuhnke wrote:
I would caution against putting much faith in the validity of
geolocation or site ID by reverse DNS PTR records. There are a vast
number of unmaintained, ancient, stale, erroneous or wildly wrong PTR
records out there. I can name at
Once upon a time, Valdis Klētnieks said:
> I wonder what year we'll get to a point where less than half of NANOG's
> membership was around when UUNet was. We're probably there already.
> And likely coming up on when less than half the people know what it
> was, other than myth and legend
I
On Mon, 29 Apr 2019 16:16:06 -0500, Bryan Holloway said:
> I still see references to UUNet in some reverse PTRs.
>
> So, uh, yeah.
I wonder what year we'll get to a point where less than half of NANOG's
membership was around when UUNet was. We're probably there already.
And likely coming up on
ekuhnke> I would caution against putting much faith in the validity of
ekuhnke> geolocation or site ID by reverse DNS PTR records. There are a
ekuhnke> vast number of unmaintained, ancient, stale, erroneous or
ekuhnke> wildly wrong PTR records out there. I can name at least a half
ekuhnke> dozen
On 4/29/19 3:13 PM, Eric Kuhnke wrote:
I would caution against putting much faith in the validity of
geolocation or site ID by reverse DNS PTR records. There are a vast
number of unmaintained, ancient, stale, erroneous or wildly wrong PTR
records out there. I can name at least a half dozen
I would caution against putting much faith in the validity of geolocation
or site ID by reverse DNS PTR records. There are a vast number of
unmaintained, ancient, stale, erroneous or wildly wrong PTR records out
there. I can name at least a half dozen ISPs that have absorbed other ASes,
some of
Hi NANOG,
To support Internet topology analysis efforts, I have been working on
an algorithm to automatically detect router names inside hostnames
(PTR records) for router interfaces, and build regular expressions
(regexes) to extract them. By "router name" inside the hostname, I
mean a
19 matches
Mail list logo
