- Test - lists.nanog.org

Is there anyone from ASPEWS on this list?
by William Pitcock 16 Dec '09

16 Dec '09

Hi, ASPEWS is listing 216.83.32.0/20 as being associated with the whole Atrivo incident of 2008. My memory does not recall 216.83.32.0/20 being involved, nor the provider that belongs to. So it'd be cool if I could you know, talk to someone who has involvement with that, because frankly, I do not see why it is listed as having any involvement with Atrivo. Also, the fact that Atrivo is *dead* and this stuff is still listed means that anyone who gets those blocks from ARIN next are basically screwed. Which kind of sucks. William

10 23

L.A Area routing issues?
by Ray Sanders 16 Dec '09

16 Dec '09

Anyone in in the greater L.A area experiencing routing/traffic issues? Some of our remote users in L.A (various ISP's ) are having difficulty reaching some of our systems here in Phoenix. We are on Carpathia and Cogent here. Thanks "Prediction is very difficult, especially about the future." - Niels Bohr -- Ray Sanders Linux Administrator Village Voice Media Office: 602-744-6547 Cell: 602-300-4344

1 0

Conficker may be forgotten, but it's not gone..
by Andre M. DiMino 16 Dec '09

16 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shadowserver is happy to announce a new set of statistics and charts highlighting the widespread infection & propagation of Conficker. We thought it would be of interest to illustrate the depth and extent of how Conficker truly affects a worldwide scope of providers. While much public attention has faded since the widely publicized April 1st 2009 "attack date", it's quite evident that Conficker still maintains a huge foothold on many computer systems worldwide. Hopefully this report will again raise public awareness to a 6.5M node botnet and drive remediation efforts from the providers themselves, as well as the average computer user. Shadowserver hopes you find these stats and charts as interesting as we have. This is a dynamic page, so you can watch trends and remediation efforts over time. As always, we're interested in how folks use and benefit from our data and reports. Feel free to drop us a note anytime and give us your feedback. Shadowserver has posted a new blog about this at: http://www.shadowserver.org/wiki/pmwiki.php/Calendar/20091216 The Conficker stats and charts page can be found here: http://www.shadowserver.org/wiki/pmwiki.php/Stats/Conficker - -- Andre' M. Di Mino - SemperSecurus The Shadowserver Foundation http://www.shadowserver.org Skype: sempersecurus AIM: sempersecurus "Make sure that nobody pays back wrong for wrong, but always try to be kind to each other and to everyone else." 1 Thessalonians 5:15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkso3UkACgkQPJaIJoADD66V0gCbBeCQJnf8byeBdyw89aNW/EJR DuYAoL+UNIkwnCTprSqS1D4NtCM2NllS =frkR -----END PGP SIGNATURE-----

1 0

Need to contact someone with Verisign
by Scott M. Likens 16 Dec '09

16 Dec '09

Hi, Long story short I am a customer of 1and1.com for the domain adappsolutions.com, we moved our datacenter roughly 60-days ago and updated our records with 1and1. However it is now December 15th and when I go here, http://registrar.verisign-grs.com/cgi-bin/whois?whois_nic=ns2.adappsolution… I see it pointing to the incorrect address, as well as ns1.adappsolutions.com I have updated all the records I can find on 1and1.com and still there does not seem to be a way for this update to occur? So if someone can contact me off list, so I can get this addressed ASAP that would be wonderful. Thanks, Sincerely, Scott M. Likens

1 1

ADMIN: List FAQ/Monthly Post.
by NANOG Mail List Committee 16 Dec '09

16 Dec '09

This 100-line document contains 62% of what you need to know to avoid annoying 10,000 people in your email to the NANOG list. It also contains pointers to another 23%. Please take 5 minutes to read it before you post [again]. General Information =================== About NANOG: http://www.nanog.org/about/ NANOG News: http://www.nanog.org/ NANOG lists and AUP: http://www.nanog.org/mailinglist/ NANOG List FAQ: http://www.nanog.org/mailinglist/listfaqs/ To Subscribe or Unsubscribe from the list: http://mailman.nanog.org/mailman/listinfo/nanog To contact the list's admins: admins(a)nanog.org Posting Policy ============== The NANOG list has over 10,000 subscribers so it is very easy for a thread to have scores of posts while being off-topic and only of interest to only a small proportion of subscribers. Please consider before each post if your email will be of interest to the majority of members or might alternatively be emailed directly the people of interest or posted to another forum. Please read the FAQ and AUP policy before posting for more details. Especially the following are discouraged: * Is a certain site down? Other Outages not affecting half the Internet. Please use http://downforeveryoneorjustme.com/ or a similar site. Please post to the Outages mailing list: http://wiki.outages.org * Spam Please use SPAM-L - http://spam-l.com/mailman/listinfo * Contacting People * http://puck.nether.net/netops/ * http://www.peeringdb.com * Please try other methods of contacting sites before you post to NANOG. Saying something like "I tried calling 213-555-3333 but no answer" shows you _have_ tried alternative methods first. * Political Issues * Topics such as ICANN policy, Government Policy or Law changes that do not have short term Operational impact should be avoided. * Operation topics with more specific lists * DNS - http://lists.oarci.net/mailman/listinfo/dns-operations * Email - http://www.mailop.org/ * NANOG Mailing list policy Please use the nanog-futures list or contact admins(a)nanog.org Please also avoid ================= * Sending posts to the list relevant to only one or two people on this list, such as tests or traceroutes in response to another post for comparison to those originally posted. * Jokes, Puns, amusing observations, spelling corrections. Other NANOG related lists ========================= * NANOG-futures - for discussion of the evolution of NANOG, including organizational structure, policies and procedures, and agendas for NANOG meetings. Such topics aren't appropriate for the main NANOG mailing list. http://mailman.nanog.org/mailman/listinfo/nanog-futures * nanog-attendee - For discussion of venue-specific issues relevant to attendees of the current NANOG physical meeting. http://mailman.nanog.org/mailman/listinfo/nanog-attendee * nanog-announce - For announcements of NANOG meetings an other Important NANOG related announcements. Low traffic and all posts are also sent to main list. http://mailman.nanog.org/mailman/listinfo/nanog-announce Other Mailing Lists =================== Information about related lists: http://www.nanog.org/mailinglist/listfaqs/otherlists.php

1 0

Cogent $1500 GigE
by Babak Pasdar 15 Dec '09

15 Dec '09

Dear List, I am getting a big push from Cogent on their full GigE for $1.50 per circuit. What are your experiences with Cogent in general? If on the fence, how would you use their service for this deal to make sense? Best Regards, Babak -- Babak Pasdar President & CEO | Certified Ethical Hacker Bat Blue Corporation | Integrity . Privacy . Availability (p) 212.461.3322 x3005 | (f) 212.584.9999 | (w) www.BatBlue.com Receive Bat Blue's Daily Security Intelligence Report Bat Blue's AS: 25885 | BGP Policy | Peering Policy Bat Blue's Legal Notice Reducing IT Security Budget, Burden & Risk - Video | Article

4 3

Root zone DNSSEC deployment web site and technical status update
by Matt Larson 15 Dec '09

15 Dec '09

The root zone DNSSEC deployment team is pleased to announce a new web site with information about the project, http://www.root-dnssec.org. The site serves as a repository for documentation and information about deploying DNSSEC in the root zone, including technical status updates. The first status update is available on the site and is included below, as well. Additional documentation will be posted as it becomes available. Important announcements and future status updates will appear in the site's RSS feed, http://www.root-dnssec.org/rss. The design team welcomes your feedback: you can reach the entire team at rootsign(a)icann.org. On behalf of the root zone DNSSEC deployment team, Matt Larson -- Status Update, December, 2009 This is the first of a series of technical status updates intended to inform a technical audience on the progress of deploying DNSSEC in the root zone of the DNS. RESOURCES Details of the project, including documentation published to date, can be found at http://www.root-dnssec.org/. We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org. DOCUMENTATION This project involves the creation of a large volume of documentation, individual components of which will be released as they have completed internal review. The following documents are expected to be released as drafts before the end of December 2009: * Root Zone DNSSEC Deployment Plan * Root Zone Trust Anchor Publication DEPLOYMENT STATUS Several root server operators have started testing a lightweight packet capture tool designed to provide a full record of priming queries received over the period covering DNSSEC deployment in the root zone. We hope this data collection will be in full production on all root servers before the end of December, providing baseline data which will allow the reaction of the system as a whole to deployment events to be observed. On 2009-12-01, the first pre-production KSR exchange between ICANN and VeriSign and the signing of the root zone within VeriSign's production infrastructure commenced. The signing, validation, measurement and monitoring infrastructure will now be subject to full internal testing. PLANNED DEPLOYMENT SCHEDULE 2009-12-01: KSR exchange, root zone signing begins, internal to VeriSign and ICANN; generation of DURZ Week of 2010-01-11: L starts to serve DURZ Week of 2010-02-08: A starts to serve DURZ Week of 2010-03-01: M, I start to serve DURZ Week of 2010-03-22: D, K, E start to serve DURZ Week of 2010-04-12: B, H, C, G, F start to serve DURZ Week of 2010-05-03: J starts to serve DURZ 2010-07-01: Distribution of validatable, production, signed root zone; publication of root zone trust anchor. (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.)

1 0

Cyclops Down?
by sjk 15 Dec '09

15 Dec '09

Is anyone else seeing cyclops down -- or is it just me? mtr -c10 -r 131.179.96.253 4. osh-2828-peer.onshore.net 0.0% 10 1.3 1.3 1.2 1.6 0.1 5. ip65-47-181-105.z181-47-65.c 0.0% 10 1.4 2.0 1.3 3.7 0.8 6. ge11-1-4d0.mcr2.chicago-il.u 0.0% 10 2.1 1.7 1.4 2.1 0.3 7. ae1d0.mcr1.chicago-il.us.xo. 0.0% 10 2.7 11.8 1.8 34.9 13.4 8. 216.156.0.161.ptr.us.xo.net 0.0% 10 62.2 62.3 62.0 62.8 0.3 9. te-3-2-0.rar3.dallas-tx.us.x 0.0% 10 61.1 61.8 61.0 64.2 1.0 10. 207.88.12.46.ptr.us.xo.net 0.0% 10 61.6 61.6 60.7 63.8 1.1 11. 207.88.12.158.ptr.us.xo.net 0.0% 10 60.7 61.0 60.7 61.7 0.4 12. lax-px1--xo-ge.cenic.net 0.0% 10 60.5 60.8 60.4 61.4 0.4 13. dc-lax-core1--lax-peer1-ge.c 0.0% 10 61.5 61.5 61.1 62.1 0.4 14. dc-lax-agg1--lax-core1-ge.ce 0.0% 10 61.1 61.6 60.8 63.5 0.9 15. dc-ucla--lax-agg1-ge-2.cenic 0.0% 10 62.0 62.6 61.7 65.1 1.3 16. border-2--core-1-ge.backbone 0.0% 10 62.4 62.4 61.8 63.4 0.5 17. core-1--mathsci-10ge.backbon 0.0% 10 61.9 61.7 61.4 62.1 0.2 18. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

3 3

Customer issue connecting to TWTelecom
by Scott Wolfe 15 Dec '09

15 Dec '09

Can someone from TW Telecom contact me offlist? I have a customer having issues connecting to a TW Telecom hosted site. Scott Wolfe Cybera, Inc 615-301-2346

1 0

Re: IP to authoritative CIDR webservices
by William Pitcock 15 Dec '09

15 Dec '09

Hi, On Mon, 2009-12-14 at 21:10 -0800, Mehmet Akcin wrote: > Current RIR whois actually does that. > > ie: search for 199.4.29 > it will show you 199.4.28/22 Yes, but it has to be parsed, and RIRs have varying whois formats. ARIN vs RIPE whois output, for example. William

3 2