Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On May 22, 2012, at 10:47 PM, Randy Bush wrote: When those servers are turned off, Customer Support folks at many ISPs will prolly want to take their accrued vacation. Amen. And there will be thousands more of them when the court order expires than existed when the Feds called him in. they could extend the court order, or prolong the do-gooder hack longer under some other pretext, increasing the underlying problem further. more infected machines and more job creation for front line support when the whitewash finally stops. According to the pretty graphs, the number of machines querying the aforementioned infrastructure is going down. Just not as fast as pretty much everyone would prefer… and the DOJ is footing the bill, and grows tired of it. So at some point, the lights are gonna be turned off. It's a shame the ISPs who have the infected users have done less to mitigate the issue. And many solutions were suggested, but all of them ended up being … perceived to be worse than just shutting it down. Or so I recall the presentation that Paul gave to a bunch of us in San Francisco back in February. Aloha, Michael. -- Please have your Internet License and Usenet Registration handy...
Re: SNMP/TCP probes from critical.io
This is HD Moore's latest experiment. It is annoying for sure but well .. he's doing it for research, and you can either acl off his probes or email him and he'll exempt your ASN from whatever scanning he is doing. On Wed, May 23, 2012 at 3:48 PM, Raoul Bhatia [IPAX] r.bha...@ipax.at wrote: * 184.154.42.194 / critical.io * 69.64.43.135 / research1.critical.io * 69.64.43.137 / research2.critical.io * 69.64.43.142 / research3.critical.io * 50.116.22.209 -- Suresh Ramasubramanian (ops.li...@gmail.com)
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On 5/23/12 1:40 AM, bmann...@vacation.karoshi.com wrote: In a modestly favorable light, ISC looks like an arms dealer (DNS redirection) to the bad guys my thought looks like a reasonably successful alternate root operator. i mention kevin dunlap as well as bill's mention of phil almquist, and there's another 4th floor of evans hall name i nay recall when caffinated. -e
RE: Current IPv6 state of US Mobile Phone Carriers
In the radio interface? Something in the GUI? Alvaro -Mensaje original- De: Tina TSOU [mailto:tina.tsou.zout...@huawei.com] Enviado el: miércoles, 23 de mayo de 2012 2:03 Para: PC; Paul Graydon CC: nanog@nanog.org Asunto: RE: Current IPv6 state of US Mobile Phone Carriers iOS 5.1 includes SLAAC and DHCPv6 client. Tina -Original Message- From: PC [mailto:paul4...@gmail.com] Sent: Tuesday, May 22, 2012 4:59 PM To: Paul Graydon Cc: nanog@nanog.org Subject: Re: Current IPv6 state of US Mobile Phone Carriers IPV6 is present, to my knowledge, on all devices on the Verizon IPV6 LTE network. I noticed its using it to communicate to Google for many of it's services when I ran a netstat. I believe they mandated support for it from any certified device. Unfortunately, it's still firewalled. On Tue, May 22, 2012 at 5:40 PM, Paul Graydon p...@paulgraydon.co.uk wrote: On 05/22/2012 01:21 PM, Cameron Byrne wrote: On May 22, 2012 4:00 PM, Paul Porterpaul.por...@gree.co.jp wrote: Hi NANOG, I'm looking for some information on the four largest US mobile phone carriers and the current state of their IPv6 infrastructure. Specifically, we are trying to figure out: 1. How much of the carrier core and edge for ATT, Verizon. T-Mobile, and Sprint are on IPv6 now? Hi, T-Mobile USA has native ipv6 to all subscribers in all of it's coverage area. But, less than 1% of subscribers use IPv6 because they do not have an IPv6 capable phone. The Nexus S and Galaxy Nexus work well. This device challenge will improve in time. Samsung is doing a good job of bringing IPv6 to Android devices. More info here That's interesting. I have a Galaxy Nexus on T-Mobile USA and it doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my wireless network at home. Doesn't seem to be anything obvious in the settings to enable or disable that. Paul ** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
RE: Current IPv6 state of US Mobile Phone Carriers
From: Christopher Morrow [mailto:morrowc.li...@gmail.com] On Tue, May 22, 2012 at 10:07 PM, Randy Carpenter rcar...@network1.net wrote: Not only does Verizon *not* have IPv6 on their LTE network, they also do *not* have IPv4, except for double-NATed rfc1918 crap that changes your IP address every couple minutes. The only way to get a stable connection is to pay them $500 to get a static public IP address. wierd, I could swear someone in my office with a galaxy-nexus-on-vzw was able to browse some ipv6-only sites. My Moto Droid RAZR is most definitely IPv6 over LTE. Jamie
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
Hi, dnschanger gonna be a mess? that's not news. Is there anywhere a page where one can type an ASN or a CIDR block and then the whois contacts get a list of IPs that still contact the unintended servers? (I had done ACL with log on borders, and resolvers did show up too. So maybe some NS pointing towards those bad blocks?) Thanks, Frank
Re: Vixie warns: DNS Changer ?blackouts? inevitable
On Wed, May 23, 2012 at 03:10:38PM +0300, Frank Habicht ge...@geier.ne.tz wrote a message of 13 lines which said: Is there anywhere a page where one can type an ASN or a CIDR block and then the whois contacts get a list of IPs that still contact the unintended servers? See http://www.dcwg.org/isps/
Re: Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Tue, 22 May 2012, Michael J Wise wrote: So at some point, the lights are gonna be turned off. It's a shame the ISPs who have the infected users have done less to mitigate the issue. To be fair, and take issue with this, it's not all on the ISPs, is it? I've been seeing our counts decrease for months, but there are some who will not/cannot get it. I am sadistically looking forward to the shutdown, admittedly.
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
- Original Message - From: bmann...@vacation.karoshi.com On Tue, May 22, 2012 at 07:14:16PM -0700, Henry Linneweh wrote: http://www.theregister.co.uk/2012/05/17/dns_changer_blackouts/ Paul certainly knows how to manipulate the press. You don't know journalists very well, do you? Paul almost certainly (p 0.995) had nothing to do with the writer's chosen appellation, and wouldn't have been able to change it if he had. Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
It makes for a more sensational story. On Wed, May 23, 2012 at 12:24 PM, Jay Ashworth j...@baylink.com wrote: - Original Message - From: bmann...@vacation.karoshi.com On Tue, May 22, 2012 at 07:14:16PM -0700, Henry Linneweh wrote: http://www.theregister.co.uk/2012/05/17/dns_changer_blackouts/ Paul certainly knows how to manipulate the press. You don't know journalists very well, do you? Paul almost certainly (p 0.995) had nothing to do with the writer's chosen appellation, and wouldn't have been able to change it if he had. Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274 -- Kyle Creyts Information Assurance Professional BSidesDetroit Organizer
Re: Current IPv6 state of US Mobile Phone Carriers
For DHCPv6 client, there is no GUI. Tina On May 23, 2012, at 4:24 AM, Alvaro Vives alvaro.vi...@consulintel.es wrote: DHCPv6 client
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On 2012-05-23, at 00:10, bmann...@vacation.karoshi.com wrote: BIND - The Berkeley Internet Naming Daemon. Berkeley Internet Name Domain, in fact. http://www.eecs.berkeley.edu/Pubs/TechRpts/1984/CSD-84-182.pdf Joe
RE: Current IPv6 state of US Mobile Phone Carriers
Here's a screenshot from 15 months ago: http://www.fix6.net/archives/2011/02/21/ipv6-live-on-verizons-lte-network/ Frank -Original Message- From: Randy Carpenter [mailto:rcar...@network1.net] Sent: Tuesday, May 22, 2012 9:07 PM To: PC Cc: nanog@nanog.org Subject: Re: Current IPv6 state of US Mobile Phone Carriers Not only does Verizon *not* have IPv6 on their LTE network, they also do *not* have IPv4, except for double-NATed rfc1918 crap that changes your IP address every couple minutes. The only way to get a stable connection is to pay them $500 to get a static public IP address. thanks, -Randy - Original Message - IPV6 is present, to my knowledge, on all devices on the Verizon IPV6 LTE network. I noticed its using it to communicate to Google for many of it's services when I ran a netstat. I believe they mandated support for it from any certified device. Unfortunately, it's still firewalled. On Tue, May 22, 2012 at 5:40 PM, Paul Graydon p...@paulgraydon.co.uk wrote: On 05/22/2012 01:21 PM, Cameron Byrne wrote: On May 22, 2012 4:00 PM, Paul Porterpaul.por...@gree.co.jp wrote: Hi NANOG, I'm looking for some information on the four largest US mobile phone carriers and the current state of their IPv6 infrastructure. Specifically, we are trying to figure out: 1. How much of the carrier core and edge for ATT, Verizon. T-Mobile, and Sprint are on IPv6 now? Hi, T-Mobile USA has native ipv6 to all subscribers in all of it's coverage area. But, less than 1% of subscribers use IPv6 because they do not have an IPv6 capable phone. The Nexus S and Galaxy Nexus work well. This device challenge will improve in time. Samsung is doing a good job of bringing IPv6 to Android devices. More info here That's interesting. I have a Galaxy Nexus on T-Mobile USA and it doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my wireless network at home. Doesn't seem to be anything obvious in the settings to enable or disable that. Paul
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
In a message written on Wed, May 23, 2012 at 12:35:05PM +0900, Randy Bush wrote: father of bind? that's news. I believe the error is in Paul Vixie's Wikipedia page, and I don't do Wikipedia editing so I won't be fixing it. http://en.wikipedia.org/wiki/Paul_Vixie In 1988, while employed by DEC, he started working on the popular internet domain name server BIND, of which he was the primary author and architect, until release 8. ISC has spent some effort on properly documenting the history of BIND, and the result of that effort is located at: http://www.isc.org/software/bind/history You'll note there are two full paragraphs and a dozen folks involved before Paul had anything to do with BIND. ISC is always interested in updating the history if folks have any additional information. Feel free to e-mail me if you think you have something important to add. -- Leo Bicknell - bickn...@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ pgpJ1lMQZ5bkZ.pgp Description: PGP signature
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On May 23, 2012, at 8:22 AM, na...@namor.ca wrote: On Tue, 22 May 2012, Michael J Wise wrote: So at some point, the lights are gonna be turned off. It's a shame the ISPs who have the infected users have done less to mitigate the issue. To be fair, and take issue with this, it's not all on the ISPs, is it? Agreed. By definition, the numbers have been falling. So somewhere, someone is doing something to lessen the coming /facepalm I've been seeing our counts decrease for months, but there are some who will not/cannot get it. I am sadistically looking forward to the shutdown, admittedly. You have your time off approved I trust? :) Aloha, Michael. -- Please have your Internet License and Usenet Registration handy...
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, May 23, 2012 at 1:40 AM, bmann...@vacation.karoshi.com wrote: Paul will be there to turn things off when they no longer make money for his company. is the dns changer thingy making money for isc?
RE: Current IPv6 state of US Mobile Phone Carriers
http://i.imgur.com/c0Bmz.jpg From a few minutes ago... On May 23, 2012 2:58 PM, Frank Bulk - iName.com frnk...@iname.com wrote: Here's a screenshot from 15 months ago: http://www.fix6.net/archives/2011/02/21/ipv6-live-on-verizons-lte-network/ Frank -Original Message- From: Randy Carpenter [mailto:rcar...@network1.net] Sent: Tuesday, May 22, 2012 9:07 PM To: PC Cc: nanog@nanog.org Subject: Re: Current IPv6 state of US Mobile Phone Carriers Not only does Verizon *not* have IPv6 on their LTE network, they also do *not* have IPv4, except for double-NATed rfc1918 crap that changes your IP address every couple minutes. The only way to get a stable connection is to pay them $500 to get a static public IP address. thanks, -Randy - Original Message - IPV6 is present, to my knowledge, on all devices on the Verizon IPV6 LTE network. I noticed its using it to communicate to Google for many of it's services when I ran a netstat. I believe they mandated support for it from any certified device. Unfortunately, it's still firewalled. On Tue, May 22, 2012 at 5:40 PM, Paul Graydon p...@paulgraydon.co.uk wrote: On 05/22/2012 01:21 PM, Cameron Byrne wrote: On May 22, 2012 4:00 PM, Paul Porterpaul.por...@gree.co.jp wrote: Hi NANOG, I'm looking for some information on the four largest US mobile phone carriers and the current state of their IPv6 infrastructure. Specifically, we are trying to figure out: 1. How much of the carrier core and edge for ATT, Verizon. T-Mobile, and Sprint are on IPv6 now? Hi, T-Mobile USA has native ipv6 to all subscribers in all of it's coverage area. But, less than 1% of subscribers use IPv6 because they do not have an IPv6 capable phone. The Nexus S and Galaxy Nexus work well. This device challenge will improve in time. Samsung is doing a good job of bringing IPv6 to Android devices. More info here That's interesting. I have a Galaxy Nexus on T-Mobile USA and it doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my wireless network at home. Doesn't seem to be anything obvious in the settings to enable or disable that. Paul
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, May 23, 2012 at 04:33:28PM -0400, Christopher Morrow wrote: On Wed, May 23, 2012 at 1:40 AM, bmann...@vacation.karoshi.com wrote: Paul will be there to turn things off when they no longer make money for his company. is the dns changer thingy making money for isc? pretty sure. a contract w/ the Feds, outsouring contracts w/ affected ISPs when the Fed deal runs out, development funding to code these kinds of fixes into future versions of software, any number of second and third order fallout. No telling how effective constent self-promotion is. One thing is clear, Paul is able to tell a great story. but its all speculation from here. ISC is well positioned to extract value from both ends of the spectrum. They have a great business model. The optics look pretty odd from here, at lesat to me however - I am very glad for: )open source )other vendors of DNS SW. /bill
Re: Current IPv6 state of US Mobile Phone Carriers
Looks like some devices have it enabled, and some do not. Does anyone have hotspot enabled? I am curious as to if IPv6 is being done via the hotspot, and how they are handling the prefix delegation. thanks, -Randy - Original Message - http://i.imgur.com/c0Bmz.jpg From a few minutes ago... On May 23, 2012 2:58 PM, Frank Bulk - iName.com frnk...@iname.com wrote: Here's a screenshot from 15 months ago: http://www.fix6.net/archives/2011/02/21/ipv6-live-on-verizons-lte-network/ Frank -Original Message- From: Randy Carpenter [mailto: rcar...@network1.net ] Sent: Tuesday, May 22, 2012 9:07 PM To: PC Cc: nanog@nanog.org Subject: Re: Current IPv6 state of US Mobile Phone Carriers Not only does Verizon *not* have IPv6 on their LTE network, they also do *not* have IPv4, except for double-NATed rfc1918 crap that changes your IP address every couple minutes. The only way to get a stable connection is to pay them $500 to get a static public IP address. thanks, -Randy - Original Message - IPV6 is present, to my knowledge, on all devices on the Verizon IPV6 LTE network. I noticed its using it to communicate to Google for many of it's services when I ran a netstat. I believe they mandated support for it from any certified device. Unfortunately, it's still firewalled. On Tue, May 22, 2012 at 5:40 PM, Paul Graydon p...@paulgraydon.co.uk wrote: On 05/22/2012 01:21 PM, Cameron Byrne wrote: On May 22, 2012 4:00 PM, Paul Porter paul.por...@gree.co.jp wrote: Hi NANOG, I'm looking for some information on the four largest US mobile phone carriers and the current state of their IPv6 infrastructure. Specifically, we are trying to figure out: 1. How much of the carrier core and edge for ATT, Verizon. T-Mobile, and Sprint are on IPv6 now? Hi, T-Mobile USA has native ipv6 to all subscribers in all of it's coverage area. But, less than 1% of subscribers use IPv6 because they do not have an IPv6 capable phone. The Nexus S and Galaxy Nexus work well. This device challenge will improve in time. Samsung is doing a good job of bringing IPv6 to Android devices. More info here That's interesting. I have a Galaxy Nexus on T-Mobile USA and it doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my wireless network at home. Doesn't seem to be anything obvious in the settings to enable or disable that. Paul
NANOG 55 Peering Track agenda and announcements
Hi All, Here's the current plan for the Peering BOF. Session will take place on Monday, June 4, 2012 from 4:30 PM to 6:00 PM in Salon D-F Please join us for a lively discussion. NANOG Peering BoF 90 minutes Introductions and PeeringDB PSA 5min Peering Personals Part I 5min LinkedIN Presentation/Discussion 20min IX Updates 5 min Peering Personals Part 2 5-10 min Pandora Presentation/Discussion 20min Mobile/Peering Changes Discussion 20 min * If you'd like to be part of new Peering Personals - a chance to announce your intention to peer - we'd love to meet you. Please email me off-list with Name, Organization, and URL in Peeringdb by next Monday. * If you're an IX and want to be part of the IX update, please email me directly for the slide template. I'll send it to you so you can submit 1-3 (no more) PowerPoint slides which can be rolled with out narration, by next Monday. * I'd also like to speak to some more folks who work for the Mobile carriers so please get in touch if you'd like to help. ~Steve http://www.pandora.com/profile/peace https://www.peeringdb.com/private/participant_view.php?id=1407 for peering requests please send to peer...@pandora.com
Re: Current IPv6 state of US Mobile Phone Carriers
On Wed, May 23, 2012 at 2:07 PM, Randy Carpenter rcar...@network1.net wrote: Looks like some devices have it enabled, and some do not. Does anyone have hotspot enabled? I am curious as to if IPv6 is being done via the hotspot, and how they are handling the prefix delegation. On T-Mobile, this code works for IPv6 + IPv4 HotSpot / WiFi tethering on the Nexus S http://dan.drown.org/android/clat/ Galaxy Nexus S ROM of the same function here https://groups.google.com/group/tmoipv6beta/browse_thread/thread/ba8aac8063735e2a Mainline Android does not yet have an IPv6 tethering feature, but the code has been pushed upstream to Android for review https://android-review.googlesource.com/#/c/34490/ Cameron
Any mail peeps from Rackspace?
Howdy, Looking for a mail admin at Rackspace to help troubleshoot some issues. Please hit me up off-list. Thank You, Mike -- Mike Lyon 408-621-4826 mike.l...@gmail.com http://www.linkedin.com/in/mlyon
vixie, father of multitudes
thanks to several folks who let me know this was going on. i hadn't even noticed that i wasn't getting nanog@. thanks to seclists.org for hosting an archive i could use. --- From: bmanning () vacation karoshi com Date: Wed, 23 May 2012 05:40:16 + On Tue, May 22, 2012 at 10:07:52PM -0700, Michael J Wise wrote: On May 22, 2012, at 9:10 PM, bmanning () vacation karoshi com wrote: On Tue, May 22, 2012 at 08:52:52PM -0700, Michael J Wise wrote: On May 22, 2012, at 8:35 PM, Randy Bush wrote: father of bind? that's news. http://boingboing.net/2012/03/29/paul-vixies-firsthand-accoun.html He was there, and Put The Fix In, to down the network. Certainly news to Phil Almquist and the entire BIND development team at UCB. Paul was at DECWRL and cut his teeth on pre-existing code. While he (and ISC) have since revised, gutted, tossed all the orginal code, rebuilt it twice - and others have done similar for their DNS software, based on the BIND code base, implementation assumptions, and with little or no ISC code, and they call it BIND as well, it would be a HUGE leap of faith to call Paul Vixie the father of BIND - The Berkeley Internet Naming Daemon. Methinks we're talking at cross purposes. maybe... :) my comment was refering to the father of bind statement. i don't describe myself that way. i inherited bind at 4.8.3 and fixed stuff. i rewrote a lot of it for 4.9. we (mostly me but with huge work by robert halley and mark andrews) rewrote most of it for bind 8.1. (there was no 8.0.) other people (not me) wrote bind 9.x. other people (mostly not the same people) are writing bind 10. if my wikipedia entry is wrong in this regard i invite folks to fix it. last i heard it's disallowed for people to edit their own entries, so i have not tried. i am not the father of anything, except four healthy kids. i do sometimes call myself the wierd uncle of the internet but father of bind is not what i mean. As for being there and Put The Fix In... Makes for great PR but in actual fact, its a bandaid that is not going to stem the tide. An actual fix would really need to change the nature of the creaky 1980's implementation artifacts that this community loves so well. I don't think we're talking about the same thing at all. Paul was there to shut down the DNS changer system and replace it with something that restored functionality to the infected machines. And I gather Paul will be one of the people who will turn the lights out on it. yes, and yes. He didn't shut down DNS Changer, he put up an equivalent system to hijack DNS traffic and direct it to the right place... SO folks didn't see any problem and the DNS Changer infection grew and got worse. When he is legally required to take his bandaide out of service, then the problem will resolve by folks who will have to clean their systems. it's true, the fbi team who powered all that stuff off and loaded it into a u-haul truck are the ones who shut down dns changer. or perhaps it was the police in estonia who arrested all those people. i'm not the shutter-downer. As for turning the lights out - that will only happen when the value of DNS hijacking drops. As it is now, ISC has placed DNS hijacking code into their mainstream code base... because DNS hijacking is so valuable to folks. In a modestly favorable light, ISC looks like an arms dealer (DNS redirection) to the bad guys -AND- (via DNSSEC) the good guys. Either way, they make money. well, no. but that seems off-topic. start a new thread if you care. (and, cc me!) And yes, I think I agree with you. Paul will be there to turn things off when they no longer make money for his company. well, no. when the court order runs out we will have to shut things down. but the money FBI is paying us for this is just to cover costs. and, it's not my company. isc is a 501(c)(3), basically a ward of the state of delaware, having no shares and therefore no shareholders. Your other comments are non-sequitur to the main issue. Perhaps I am not a member of the Paul Vixie cult of personality. so sad. When those servers are turned off, Customer Support folks at many ISPs will prolly want to take their accrued vacation. Amen. And there will be thousands more of them when the court order expires than existed when the Feds called him in. um. no. hundreds of thousands less than before the feds called ISC in. see dcwg.org. it's lovely to have so many fans. keep those cards and letters coming. (but, cc me!) paul
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, 23 May 2012 13:09:09 -0700, Leo Bicknell said: In 1988, while employed by DEC, he started working on the popular internet domain name server BIND, of which he was the primary author and architect, until release 8. ISC has spent some effort on properly documenting the history of BIND, and the result of that effort is located at: http://www.isc.org/software/bind/history You'll note there are two full paragraphs and a dozen folks involved before Paul had anything to do with BIND. One could make the case that the releases before Paul got there weren't exactly popular - how many DNS servers were in production in 1986? ;) pgpuj3fJYBq3D.pgp Description: PGP signature
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, May 23, 2012 at 5:42 PM, valdis.kletni...@vt.edu wrote: On Wed, 23 May 2012 13:09:09 -0700, Leo Bicknell said: In 1988, while employed by DEC, he started working on the popular internet domain name server BIND, of which he was the primary author and architect, until release 8. ISC has spent some effort on properly documenting the history of BIND, and the result of that effort is located at: http://www.isc.org/software/bind/history You'll note there are two full paragraphs and a dozen folks involved before Paul had anything to do with BIND. One could make the case that the releases before Paul got there weren't exactly popular - how many DNS servers were in production in 1986? ;) Please don't make me remember hosts.txt before I've had a chance to wrap up work, go home, and get some Scotch in... -- -george william herbert george.herb...@gmail.com
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On May 23, 2012, at 18:27, George Herbert george.herb...@gmail.com wrote: Please don't make me remember hosts.txt before I've had a chance to wrap up work, go home, and get some Scotch in... Come on George, hosts.txt was the good old days :) -b
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On 5/23/2012 6:35 PM, Brett Watson wrote: On May 23, 2012, at 18:27, George Herbertgeorge.herb...@gmail.com wrote: Please don't make me remember hosts.txt before I've had a chance to wrap up work, go home, and get some Scotch in... Come on George, hosts.txt was the good old days :) I still have a copy (from around 1992, so one of the very last), although much edited (and NOT 10,000 hosts, thanks). -- A picture is worth 10K words -- but only those to describe the picture. Hardly any sets of 10K words can be adequately described with pictures.
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, May 23, 2012 at 6:35 PM, Brett Watson br...@the-watsons.org wrote: On May 23, 2012, at 18:27, George Herbert george.herb...@gmail.com wrote: Please don't make me remember hosts.txt before I've had a chance to wrap up work, go home, and get some Scotch in... Come on George, hosts.txt was the good old days :) An elegant weapon, for a more civilized age? -- -george william herbert george.herb...@gmail.com
Re: vixie, father of multitudes
On May 23, 2012, at 5:28 PM, paul vixie wrote: it's lovely to have so many fans. keep those cards and letters coming. (but, cc me!) Yessir! Aloha, Michael. -- Please have your Internet License and Usenet Registration handy...
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
On Wed, May 23, 2012 at 06:42:34PM -0700, Lynda wrote: On 5/23/2012 6:35 PM, Brett Watson wrote: On May 23, 2012, at 18:27, George Herbertgeorge.herb...@gmail.com wrote: Please don't make me remember hosts.txt before I've had a chance to wrap up work, go home, and get some Scotch in... Come on George, hosts.txt was the good old days :) I still have a copy (from around 1992, so one of the very last), although much edited (and NOT 10,000 hosts, thanks). ftp://ftp.math.ethz.ch/pub/doc/hosts.txt Leftovers! -- - (2^(N-1))
Re: Vixie warns: DNS Changer ‘blackouts’ inevitable
The best policy, sometimes, when one sees something questionable on Wikipedia, is to point it out on the talk page, and trust that others will do the dirty work.. as in http://en.wikipedia.org/wiki/Talk:Paul_Vixie#.22Father_of_BIND.22 j On Wed, May 23, 2012 at 4:09 PM, Leo Bicknell bickn...@ufp.org wrote: In a message written on Wed, May 23, 2012 at 12:35:05PM +0900, Randy Bush wrote: father of bind? that's news. I believe the error is in Paul Vixie's Wikipedia page, and I don't do Wikipedia editing so I won't be fixing it. http://en.wikipedia.org/wiki/Paul_Vixie In 1988, while employed by DEC, he started working on the popular internet domain name server BIND, of which he was the primary author and architect, until release 8. ISC has spent some effort on properly documenting the history of BIND, and the result of that effort is located at: http://www.isc.org/software/bind/history You'll note there are two full paragraphs and a dozen folks involved before Paul had anything to do with BIND. ISC is always interested in updating the history if folks have any additional information. Feel free to e-mail me if you think you have something important to add. -- Leo Bicknell - bickn...@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ -- --- Joly MacFie 218 565 9365 Skype:punkcast WWWhatsup NYC - http://wwwhatsup.com http://pinstand.com - http://punkcast.com VP (Admin) - ISOC-NY - http://isoc-ny.org -- -
