Re: Enterprise DNS providers

2010-10-18 Thread seph
I haven't used UltraDNS, but given some of their unsavory sales tactics,
I'm pretty biased against them. They spend awhile spamming people, and
calling up CTOs.

seph

Jeffrey Lyon jeffrey.l...@blacklotus.net writes:

 We're using Afilias now, we had nothing short of a horrendous
 experience dealing with Neustar / UltraDNS and their uninformed, blood
 hungry sales team.

 Best regards, Jeff


 On Mon, Oct 18, 2010 at 9:23 AM, Jonas Björklund jo...@bjorklund.cn wrote:

 On Sat, 16 Oct 2010, Ken Gilmour wrote:

 Hello any weekend workers :)

 We are looking at urgently deploying an outsourced DNS provider for a
 critical domain which is currently unavailable but are having some
 difficulty. I've tried contacting UltraDNS who only allow customers from
 US
 / Canada to sign up (we are in Malta) and their Sales dept are closed, and
 Easy DNS who don't have .com.mt as an option in the dropdown for
 transferring domain names (and also support is closed).

 I have worked for one of the biggest poker networks and we used UltraDNS.
 The company was first operated from Sweden and later Austria.

 /Jonas





 -- 
 Jeffrey Lyon, Leadership Team
 jeffrey.l...@blacklotus.net | http://www.blacklotus.net
 Black Lotus Communications - AS32421
 First and Leading in DDoS Protection Solutions



Re: Juniper firewalls - SSG or SRX

2010-04-19 Thread seph
I'm with Owen. I have nothing good to say about ScreenOS. In contrast
JunOS has been great.

seph

Owen DeLong o...@delong.com writes:

 Much.. Go SRX over SSG every time.  For anything that doesn't have an
 SRX analog, consider the J-series.

 SRX/J-Series == JunOS == Good.
 SSG Series == ScreenOS == @)#$*#@)$(*!)(@$...@$

 Just my $0.02 having dealt extensively with both environments over the
 years.

 Owen

 On Apr 19, 2010, at 5:32 PM, Jeffrey Negro wrote:

 Has anyone on Nanog had any hands on experience with the lower end of the
 new SRX series Junipers?  We're looking to purchase two new firewalls, and
 I'm debating going with SSG series or to make the jump to the SRX line.  Any
 input, especially about the learning curve jumping from ScreenOS to JunOS
 would be greatly appreciated.  Thank you in advance.
 
 Jeffrey



Re: Cogent leaking /32s?

2009-10-02 Thread seph
ML m...@kenweb.org writes:

 I received an alert from Cyclops telling me a probe in AS513 had seen
 a /32 that I announce to Cogent for one of our BGP sessions.

 Did anyone else see this?

cyclops alerted me that the /32s my routers use got announced. I'm still
tying to figure out what's up. They're not routes I announce, and as far
as I can tell, they were announced with a cern next hop.

seph



Re: Cogent leaking /32s?

2009-10-02 Thread seph
I called cogent. Best guess is that they leaked the /32 announcements
that people do for the peer a/b stuff. They normally filter them, and
don't have any recommendation about whether or not to set no export.

seph

seph s...@directionless.org writes:

 ML m...@kenweb.org writes:

 I received an alert from Cyclops telling me a probe in AS513 had seen
 a /32 that I announce to Cogent for one of our BGP sessions.

 Did anyone else see this?

 cyclops alerted me that the /32s my routers use got announced. I'm still
 tying to figure out what's up. They're not routes I announce, and as far
 as I can tell, they were announced with a cern next hop.

 seph



Re: Cogent input

2009-06-11 Thread seph
Here as well. We're a small content provider, and we have cogent as one
of our ISPs. Though I wouldn't feel comfortable using only them, my
experience has been pretty good. Their NOC is competent, and service has
been reliable.

seph

Bret Clark bcl...@spectraaccess.com writes:

 I hate when these questions get asked, because as the saying goes...a
 person happy with a service will only tell one other person, but a
 person unhappy with a service with tell ten other people.  So I think a
 lot of times you'll get skewed responses...but with that said, we've
 been using Cogent now for a year and no complaints at all. Had some
 minor downtime back in April due to a hardware failure, but Cogent
 responded extremely quickly, scheduled an emergency maintainance and had
 us  running rather quickly. Face it, hardware problems happen so I can't
 blame Cogent on the failure. The few times I've dealt with their tech
 support group I found 99% of them very knowledgeable and I know that
 when we initially turned on the link they went the extra mile to resolve
 some initial problems during the weekend time frame. 

 My 2 cents and with any provider mileage will vary,
 Bret



 On Thu, 2009-06-11 at 15:01 +0100, Andrew Mulholland wrote:

 At $JOB-1 we used Cogent.
 
 Lots of horror stories had been heard about them.
 
 We didn't have such problems.
 
 Had nx1Gig from them.
 
 On the few occasions where we had some slight issues, I was happy to
 be able to get through to some one useful on the phone quickly, and
 not play pass the parcel with call centre operatives.
 
 
 and at least in the quantities we were buying they were significantly
 better value than others, which was the primary reason we went with
 them.
 
 
 
 andrew
 
 
 
 On Thu, Jun 11, 2009 at 2:55 PM, Paul Stewartpstew...@nexicomgroup.net 
 wrote:
  Our experience with them was at least one major (longer than an hour)
  outages PER MONTH and many of those times they were black holing our
  routes in their network which was the most damaging aspect.  The outages
  were one thing but when our routes still somehow managed to get
  advertised in their network (even though our BGP session was down) that
  really created issues.  I have heard from some nearby folks who still
  have service that it's gotten better, but we are also in the regional
  offering when it comes to IP Transit and have sold connections to many
  former Cogent customers who were fed up and left.
 
  I have found with Cogent that you will get a LOT of varying opinions on
  them - there are several other players (at least in our market) that are
  priced very similar now and have a better history behind them.
 
  The specific de-peering issues never effected us much due to enough
  diversity in our upstreams and a fair amount of direct/public peering...
 
  Thanks,
 
  Paul
 
 
 
  -Original Message-
  From: Justin Shore [mailto:jus...@justinshore.com]
  Sent: Thursday, June 11, 2009 9:47 AM
  To: NANOG
  Subject: Cogent input
 
  I'm in search of some information about Cogent, it's past, present and
  future.  I've heard bits and pieces about Cogent's past over the years
  but by no means have I actively been keeping up.
 
  I'm aware of some (regular?) depeering issues.  The NANOG archives have
  given me some additional insight into that (recurring?) problem.  The
  reasoning behind the depeering events is a bit fuzzy though.  I would be
 
  interested in people's opinion on whether or not they should be consider
 
  for upstream service based on this particular issue.  Are there any
  reasonable mitigation measures available to Cogent downstreams if
  (when?) Cogent were to be depeered again?  My understanding is that at
  least on previous depeering occasion, the depeering partner simply
  null-routed all prefixes being received via Cogent, creating a blackhole
 
  essentially.  I also recall reading that this meant that prefixes being
  advertised and received by the depeering partner from other peers would
  still end up in the blackhole.  The only solution I would see to this
  problem would be to shut down the BGP session with Cogent and rely on a
  2nd upstream.  Are there any other possible steps for mitigation in a
  depeering event?
 
  I also know that their bandwidth is extremely cheap.  This of course
  creates an issue for technical folks when trying to justify other
  upstream options that cost significantly more but also don't have a
  damaging history of getting depeered.
 
  Does Cogent still have an issue with depeering?  Are there any
  reasonable mitigation measures or should a downstream customer do any
  thing in particular to ready themselves for a depeering event?  Does
  their low cost outweigh the risks?  What are the specific risks?
 
  Thanks
   Justin
 
 
 
 
 
  
 
  The information transmitted is intended only for the person or entity to 
  which it is addressed

Re: LoA (Letter of Authorization) for Prefix Filter Modification?

2008-09-19 Thread seph
Stephen Sprunk [EMAIL PROTECTED] writes:

 Azinger, Marla wrote:
 I use RWHOIS for proof of who we assign and allocate address space to.  


 How is _you_ showing information in an RWHOIS server that _you_
 control in any way proving that the holder of a address block is
 authorizing _you_ to advertise it on their behalf?

At least in my case, it's not *my* rwhois server. My first ISP lists me
as the owner/user/whatever in *their* rwhois server, and my second ISP
considers that authoritative.

seph