[IFWP] i-DNS.net International Root Sync Report Mon Sep 10 05:56:49 EDT 2001
i-DNS.net International Root Sync report for Mon Sep 10 05:56:49 EDT 2001 http://www.i-DNS.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ AI - ERROR detected in zone .AI >>> delete ns A.I-DNS.NET. from root >>> delete ns B.I-DNS.NET. from root >>> delete ns C.I-DNS.NET. from root >>> delete ns D.I-DNS.NET. from root >>> delete ns E.I-DNS.NET. from root >>> delete ns F.I-DNS.NET. from root ZR - WARNING tld lookup on IDNS rootserver 208.184.174.7 FAILED
[IFWP] The PacificRoot Root Sync Report Mon Sep 10 05:54:44 EDT 2001
The PacificRoot Root Sync report for Mon Sep 10 05:54:44 EDT 2001 http://www.pacificroot.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BG - ERROR detected in zone .BG <<< add ns NS-EXT.VIX.COM. to root <<< add ns NS2.DIGSYS.BG. to root >>> delete ns ADMII.ARL.MIL. from root BM - ERROR detected in zone .BM <<< add ns AUTH02.NS.UU.NET. to root <<< add ns NS2.IBL.BM. to root BZ - ERROR detected in zone .BZ <<< add ns A3.NSTLD.COM. to root <<< add ns B3.NSTLD.COM. to root <<< add ns C3.NSTLD.COM. to root <<< add ns D3.NSTLD.COM. to root <<< add ns E3.NSTLD.COM. to root <<< add ns F3.NSTLD.COM. to root <<< add ns G3.NSTLD.COM. to root <<< add ns L3.NSTLD.COM. to root >>> delete ns DAISY.EE.UND.AC.ZA. from root >>> delete ns NS.RIPE.NET. from root >>> delete ns RIP.PSG.COM. from root >>> delete ns YARRINA.CONNECT.COM.AU. from root COM - ERROR detected in zone .COM >>> delete ns NS1.NAMESLINGER.COM. from root >>> delete ns NS2.NAMESLINGER.COM. from root CX - ERROR detected in zone .CX <<< add ns NS2.CIX.CX. to root <<< add ns NS2.COCONUTCOMPUTING.NET. to root <<< add ns NS5.NETDNS.CO.NZ. to root >>> delete ns NS.CIX.CX. from root >>> delete ns NS0.PLANET-THREE.COM. from root >>> delete ns NS1.CX.ESCROW.IOCOMM.NET.CX. from root >>> delete ns NS2.PLANET-THREE.NET. from root GG - ERROR detected in zone .GG <<< add ns NS2.DNS.NET.NZ. to root >>> delete ns RS.ISLES.NET. from root INT - ERROR detected in zone .INT <<< add ns NS.ICANN.ORG. to root JE - ERROR detected in zone .JE <<< add ns NS2.DNS.NET.NZ. to root >>> delete ns RS.ISLES.NET. from root KR - ERROR detected in zone .KR <<< add ns KR2ND.HITEL.NET. to root <<< add ns KR2ND.KORNET.NET. to root <<< add ns USNS.DACOM.CO.KR. to root >>> delete ns NIS2.HITEL.NET. from root >>> delete ns NS.KORNET.NET. from root KZ - ERROR detected in zone .KZ <<< add ns NS.NIC.KZ. to root >>> delete ns NS.RELCOM.KZ. from root MO - ERROR detected in zone .MO <<< add ns NS2.CUHK.EDU.HK. to root <<< add ns NS3.UMAC.MO. to root >>> delete ns HKUXB.HKU.HK. from root >>> delete ns NS.UU.NET. from root NG - ERROR detected in zone .NG >>> delete ns ITGBOX.IAT.CNR.IT. from root NZ - ERROR detected in zone .NZ <<< add ns NS2.DNS.NET.NZ. to root <<< add ns NS3.DNS.NET.NZ. to root <<< add ns NS4.DNS.NET.NZ. to root >>> delete ns NS1.CLEAR.NET.NZ. from root >>> delete ns NS2.CLEAR.NET.NZ. from root >>> delete ns NS99.WAIKATO.AC.NZ. from root >>> delete ns RATA.VUW.AC.NZ. from root PM - ERROR detected in zone .PM <<< add ns NS3.NIC.FR. to root PT - ERROR detected in zone .PT <<< add ns NS2.DNS.PT. to root >>> delete ns CIUP1.NCC.UP.PT. from root RE - ERROR detected in zone .RE <<< add ns NS3.NIC.FR. to root SG - ERROR detected in zone .SG <<< add ns DNSSEC5.SINGNET.COM.SG. to root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root UG - ERROR detected in zone .UG <<< add ns DEMON.MTN.CO.UG. to root <<< add ns NS.ICANN.ORG. to root <<< add ns NS.SANYUTEL.COM. to root <<< add ns WEB.EAHD.OR.UG. to root >>> delete ns RIP.PSG.COM. from root US - ERROR detected in zone .US >>> delete ns ADMII.ARL.MIL. from root VC - ERROR detected in zone .VC <<< add ns NS2.VC.TUCOWS.NET. to root >>> delete ns TRANTOR.UMD.EDU. from root WF - ERROR detected in zone .WF <<< add ns NS3.NIC.FR. to root YT - ERROR detected in zone .YT <<< add ns NS3.NIC.FR. to root ZM - ERROR detected in zone .ZM <<< add ns NS2.ZAMNET.ZM. to root >>> delete ns PUKU.UNZA.ZM. from root ZR - WARNING tld lookup on PACROOT rootserver 204.107.129.3 FAILED
[IFWP] AlterNIC Root Sync Report Mon Sep 10 05:48:34 EDT 2001
AlterNIC Root Sync report for Mon Sep 10 05:48:34 EDT 2001 http://www.alternic.org/ (c) The dot.GOD Registry @ http://www.dot-god.com/ AC - ERROR detected in zone .AC <<< add ns NS.NIC.AC. to root AD - ERROR detected in zone .AD <<< add ns VIVALDI.TELEPAC.PT. to root >>> delete ns DNS3.AD. from root >>> delete ns NS2.TELEPAC.PT. from root >>> delete ns SUN.REDIRIS.ES. from root AE - ERROR detected in zone .AE >>> delete ns NS3.EMIRATES.NET.AE. from root AF - ERROR detected in zone .AF >>> delete ns NS3.NETNAMES.NET. from root AI - ERROR detected in zone .AI >>> delete ns A.I-DNS.NET. from root >>> delete ns B.I-DNS.NET. from root >>> delete ns C.I-DNS.NET. from root >>> delete ns D.I-DNS.NET. from root >>> delete ns E.I-DNS.NET. from root >>> delete ns F.I-DNS.NET. from root AM - ERROR detected in zone .AM >>> delete ns AUTH02.NS.UU.NET. from root >>> delete ns MUNNARI.OZ.AU. from root >>> delete ns NS.NIC.AM. from root >>> delete ns STYX.AIC.NET. from root AO - ERROR detected in zone .AO >>> delete ns DNS.FCCN.PT. from root AR - ERROR detected in zone .AR >>> delete ns RELAY1.MECON.AR. from root AS - ERROR detected in zone .AS >>> delete ns DNS.RIPE.NET. from root >>> delete ns JFK.NS.GDNS.NET. from root AW - ERROR detected in zone .AW <<< add ns NS1-AUTH.SPRINTLINK.NET. to root <<< add ns NS2-AUTH.SPRINTLINK.NET. to root <<< add ns NS2.4AW.COM. to root <<< add ns NS3-AUTH.SPRINTLINK.NET. to root >>> delete ns NS.ICANN.ORG. from root >>> delete ns NS.RIPE.NET. from root >>> delete ns NS1.SETARNET.AW. from root AZ - ERROR detected in zone .AZ >>> delete ns NS1.DEMOS.NET. from root BA - ERROR detected in zone .BA <<< add ns NS.BA. to root >>> delete ns BOSNA.UTIC.NET.BA. from root >>> delete ns NS1.BIH.NET.BA. from root >>> delete ns STARATILAVA.UTIC.NET.BA. from root BF - ERROR detected in zone .BF <<< add ns ORSTOM.RIO.NET. to root >>> delete ns NS.IRD.FR. from root BH - ERROR detected in zone .BH <<< add ns SV10.BATELCO.COM.BH. to root >>> delete ns NS3.BATELCO.COM.BH. from root BI - ERROR detected in zone .BI >>> delete ns MUNNARI.OZ.AU. from root >>> delete ns NS.NIC.BI. from root BJ - ERROR detected in zone .BJ >>> delete ns NAKAYO.LELAND.BJ. from root >>> delete ns NS.RIPE.NET. from root BO - ERROR detected in zone .BO >>> delete ns NS.NIC.CL. from root BT - ERROR detected in zone .BT <<< add ns NS.RIPE.NET. to root >>> delete ns DNS.RIPE.NET. from root BW - ERROR detected in zone .BW <<< add ns DAISY.EE.UND.AC.ZA. to root >>> delete ns NS1.BTC.BW. from root >>> delete ns NS1.GSL.NET. from root >>> delete ns NS2.GSL.NET. from root >>> delete ns VPSM.BTC.BW. from root CC - ERROR detected in zone .CC >>> delete ns NS2.GLOBALDNS.COM. from root CD - ERROR detected in zone .CD <<< add ns DNS.NIC.BI. to root >>> delete ns DNS.NIC.CD. from root >>> delete ns NS1.KEY-SYSTEMS.NET. from root >>> delete ns NS2.KEY-SYSTEMS.NET. from root >>> delete ns NS3.KEY-SYSTEMS.NET. from root CF - ERROR detected in zone .CF >>> delete ns NS.NIC.CF. from root >>> delete ns RES.NIC.CF. from root >>> delete ns XYLOS.RCA.CF. from root CG - ERROR detected in zone .CG <<< add ns DNS.NIC.BI. to root >>> delete ns DNS.NIC.CG. from root >>> delete ns MUNNARI.OZ.AU. from root CI - ERROR detected in zone .CI >>> delete ns NS1.NIC.CI. from root CL - ERROR detected in zone .CL <<< add ns NS.FIRSTCOM.CL. to root <<< add ns NS.RIPE.NET. to root >>> delete ns DNS.RIPE.NET. from root >>> delete ns ICT.UCHILE.CL. from root >>> delete ns NS.CEC.UCHILE.CL. from root >>> delete ns NS.RDC.CL. from root >>> delete ns NS2.GISC.CL. from root >>> delete ns SUNSITE.DCC.UCHILE.CL. from root >>> delete ns TERMINUS.REUNA.CL. from root >>> delete ns UCHILE.CL. from root CM - ERROR detected in zone .CM <<< add ns NS.ITU.CH. to root <<< add ns NS.RIPE.NET. to root CN - ERROR detected in zone .CN >>> delete ns DNS3.CNNIC.NET.CN. from root >>> delete ns DNS4.CNNIC.NET.CN. from root >>> delete ns DNS5.CNNIC.NET.CN. from root CO - ERROR detected in zone .CO <<< add ns NYU.EDU. to root <<< add ns SAELL.CC.COLUMBIA.EDU. to root >>> delete ns CMCL2.NYU.EDU. from root >>> delete ns CUNIXD.CC.COLUMBIA.EDU. from root CU - ERROR detected in zone .CU <<< add ns NS.RIPE.NET. to root >>> delete ns NS.CUBA.CU. from root >>> delete ns NS2.CENIAI.NET.CU. from root CX - ERROR detected in zone .CX <<< add ns NS2.CIX.CX. to root >>> delete ns NS.CIX.CX. from root DE - ERROR detected in zone .DE >>> delete ns DNS2.DENIC.DE. from root DJ - ERROR detected in zone .DJ >>> delete ns NS.RIPE.NET. from root DM - ERROR detected in zone .DM <<< add ns DOMDNS1.DOTDM.NET. to root >>> delete ns DOMNS1.DOTDM.NET. from root >>> delete ns NS1.DOTDM.NET. from root >>> delete ns NS2.CCSRS.NET. from root EE - ERROR detected in zone .EE >>> delete ns DNS.ESTPAK.EE. from root >>> delete ns KADRI.UT.EE. from root >>> delete ns NS.
[IFWP] International Root Server Confederation Root Sync Report Mon Sep 10 05:42:30 EDT 2001
International Root Server Confederation Root Sync report for Mon Sep 10 05:42:30 EDT 2001 http://www.irsc.ah.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ AI - ERROR detected in zone .AI <<< add ns NS1.OFFSHORE.AI. to root <<< add ns NS1.PAIR.COM. to root <<< add ns NS1.REDHAT.COM. to root >>> delete ns NS.C2.NET. from root >>> delete ns NS.HYPEREALITY.CO.UK. from root >>> delete ns NS2.INFONEX.NET. from root AT - ERROR detected in zone .AT <<< add ns NS3.AUSTRIA.EU.NET. to root <<< add ns NS7.UNIVIE.AC.AT. to root >>> delete ns ALIJKU01.EDVZ.UNI-LINZ.AC.AT. from root >>> delete ns NS.AUSTRIA.EU.NET. from root AW - ERROR detected in zone .AW <<< add ns NS2.4AW.COM. to root >>> delete ns NS1.SETARNET.AW. from root BE - ERROR detected in zone .BE <<< add ns MASTER.DNS.BE. to root >>> delete ns NS.DNS.BE. from root >>> delete ns SPARKY.ARL.MIL. from root BG - ERROR detected in zone .BG <<< add ns GRDNS.ICS.FORTH.GR. to root <<< add ns NS-EXT.VIX.COM. to root <<< add ns NS2.DIGSYS.BG. to root >>> delete ns ADMII.ARL.MIL. from root >>> delete ns PYTHIA.FORTHNET.GR. from root BI - ERROR detected in zone .BI <<< add ns DNS.NIC.BI. to root >>> delete ns DNS.NIC.CD. from root BM - ERROR detected in zone .BM <<< add ns AUTH02.NS.UU.NET. to root <<< add ns NS2.IBL.BM. to root >>> delete ns SPARKY.ARL.MIL. from root BO - ERROR detected in zone .BO <<< add ns AUTH100.NS.UU.NET. to root >>> delete ns WARA.BOLNET.BO. from root BZ - ERROR detected in zone .BZ <<< add ns A3.NSTLD.COM. to root <<< add ns B3.NSTLD.COM. to root <<< add ns C3.NSTLD.COM. to root <<< add ns D3.NSTLD.COM. to root <<< add ns E3.NSTLD.COM. to root <<< add ns F3.NSTLD.COM. to root <<< add ns G3.NSTLD.COM. to root <<< add ns L3.NSTLD.COM. to root >>> delete ns DAISY.EE.UND.AC.ZA. from root >>> delete ns NS.RIPE.NET. from root >>> delete ns RIP.PSG.COM. from root >>> delete ns YARRINA.CONNECT.COM.AU. from root CA - ERROR detected in zone .CA <<< add ns MERLE.CIRA.CA. to root <<< add ns NS3.UTORONTO.CA. to root <<< add ns RS0.NETSOL.COM. to root >>> delete ns DNS2.UTCC.UTORONTO.CA. from root >>> delete ns RS0.INTERNIC.NET. from root CC - ERROR detected in zone .CC <<< add ns NS1.TOKYO.JP.NETDNS.COM. to root CD - ERROR detected in zone .CD <<< add ns DNS.NIC.BI. to root >>> delete ns DNS.NIC.CD. from root CG - ERROR detected in zone .CG <<< add ns DNS.NIC.BI. to root >>> delete ns DNS.NIC.CD. from root CH - ERROR detected in zone .CH <<< add ns CCTLD.TIX.CH. to root >>> delete ns NS1.IP-PLUS.NET. from root CK - ERROR detected in zone .CK >>> delete ns NS1.WAIKATO.AC.NZ. from root CL - ERROR detected in zone .CL <<< add ns ANTONIA.WEBHOST.CL. to root <<< add ns NS.RIPE.NET. to root >>> delete ns SPARKY.ARL.MIL. from root CN - ERROR detected in zone .CN <<< add ns DNS2.CNNIC.NET.CN. to root <<< add ns NS.CERNET.NET. to root >>> delete ns DNS.EDU.CN. from root >>> delete ns IRAUN1.IRA.UKA.DE. from root >>> delete ns NS.CN.NET. from root >>> delete ns NS.EU.NET. from root >>> delete ns NS.SESQUI.NET. from root >>> delete ns NS.UU.NET. from root CO - ERROR detected in zone .CO <<< add ns SAELL.CC.COLUMBIA.EDU. to root >>> delete ns CUNIXD.CC.COLUMBIA.EDU. from root COM - ERROR detected in zone .COM <<< add ns B.GTLD-SERVERS.NET. to root <<< add ns D.GTLD-SERVERS.NET. to root <<< add ns E.GTLD-SERVERS.NET. to root <<< add ns G.GTLD-SERVERS.NET. to root <<< add ns L.GTLD-SERVERS.NET. to root >>> delete ns A.ROOT-SERVERS.NET. from root >>> delete ns E.ROOT-SERVERS.NET. from root >>> delete ns F.ROOT-SERVERS.NET. from root >>> delete ns G.ROOT-SERVERS.NET. from root CX - ERROR detected in zone .CX <<< add ns NS1.CCSRS.NET. to root <<< add ns NS2.CCSRS.NET. to root <<< add ns NS2.CIX.CX. to root <<< add ns NS2.COCONUTCOMPUTING.NET. to root <<< add ns NS5.NETDNS.CO.NZ. to root >>> delete ns NS.CIX.CX. from root >>> delete ns NS0.PLANET-THREE.COM. from root >>> delete ns NS2.PLANET-THREE.NET. from root CY - ERROR detected in zone .CY <<< add ns NS2.UCY.AC.CY. to root >>> delete ns NICOSIA.CCS.UCY.AC.CY. from root CZ - ERROR detected in zone .CZ <<< add ns NS-EXT.VIX.COM. to root >>> delete ns SPARKY.ARL.MIL. from root DE - ERROR detected in zone .DE <<< add ns SSS-AT.DENIC.DE. to root <<< add ns SSS-NL.DENIC.DE. to root >>> delete ns AUTH61.NS.UU.NET. from root >>> delete ns NS.RIPE.NET. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root >>> delete ns URANUS.DAIMI.AAU.DK. from root DM - ERROR detected in zone .DM <<< add ns DOMDNS1.DOTDM.NET. to root <<< add ns NS1.CCSRS.NET. to root <<< add ns NS1.LONDON.UK.NETDNS.COM. to root <<< add ns NS1.NEWYORK.US.NETDNS.COM. to root <<< add ns NS1.SANFRANCISCO.US.NETDNS.COM. to root <<< add ns NS1.SEATTLE.US.NETDNS.COM. to root <<< add ns NS1.TOKYO.JP.NETDNS.COM. to root >>> delete ns TRANTOR.UMD.EDU. from root >>> delete ns UPR1.UPR.CLU.E
[IFWP] Common Interest Network Information Center Society Root Sync Report Mon Sep 10 05:40:40 EDT 2001
Common Interest Network Information Center Society Root Sync report for Mon Sep 10 05:40:40 EDT 2001 http://cinic.org (c) The dot.GOD Registry @ http://www.dot-god.com/ BG - ERROR detected in zone .BG <<< add ns NS-EXT.VIX.COM. to root <<< add ns NS2.DIGSYS.BG. to root >>> delete ns ADMII.ARL.MIL. from root BZ - ERROR detected in zone .BZ <<< add ns A3.NSTLD.COM. to root <<< add ns B3.NSTLD.COM. to root <<< add ns C3.NSTLD.COM. to root <<< add ns D3.NSTLD.COM. to root <<< add ns E3.NSTLD.COM. to root <<< add ns F3.NSTLD.COM. to root <<< add ns G3.NSTLD.COM. to root <<< add ns L3.NSTLD.COM. to root >>> delete ns DAISY.EE.UND.AC.ZA. from root >>> delete ns NS.RIPE.NET. from root >>> delete ns RIP.PSG.COM. from root >>> delete ns YARRINA.CONNECT.COM.AU. from root KR - ERROR detected in zone .KR <<< add ns KR2ND.HITEL.NET. to root <<< add ns KR2ND.KORNET.NET. to root <<< add ns USNS.DACOM.CO.KR. to root >>> delete ns NIS2.HITEL.NET. from root >>> delete ns NS.KORNET.NET. from root NG - ERROR detected in zone .NG >>> delete ns ITGBOX.IAT.CNR.IT. from root SG - ERROR detected in zone .SG <<< add ns DNSSEC5.SINGNET.COM.SG. to root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root VC - ERROR detected in zone .VC <<< add ns NS2.VC.TUCOWS.NET. to root >>> delete ns TRANTOR.UMD.EDU. from root ZR - WARNING tld lookup on legacy US rootserver A.ROOT-SERVERS.NET FAILED
[IFWP] a moment of silence for Mike Muuss - confirmation? (fwd)
a moment of silence as we honour a network great. I-95 Accident claims life Churchville, Md - (AP) A double accident Monday night on Interstate 95 in Harford County killed a Havre de Grace man. State police say 42-year-old Michael Muuss died when his car hit a vehicle left partially in the road after the first crash. Muuss' car then spun into the path of a tractor-trailer, which pushed him into a vehicle stopped on the right shoulder to help victims of the earlier crash. The truck driver was taken to Harford Memorial Hospital. The accidents occurred about 9:30 pm on the northbound side of the highway in Churchville. The first involved two cars and a tractor-trailer. A driver in that crash was treated at Harford Memorial and released. Police say it's not clear why either accident occurred. No one has been charged, but the investigation is continuing. Traffic was able to get by for most of the night, but it took until 2 am before all lanes were opened. > From: Sean Donelan <[EMAIL PROTECTED]> > Subject: The author of PING is reported dead > > Since many network operators consider PING as one of their essential > tools, I thought this would be of interest to the list. > > I haven't been able to confirm this, but I haven't been able > to reach Mike. > > Forwarded message: > > >Subject: The Creator of Ping is dead... > > > >Mike Muuss, the author of the PING program used on networks everywhere, > >died last night in a traffic accident on US route 95 in Maryland. He was > >an alumnus of Johns Hopkins (BS1978 or 1979 I think). > > > >Funeral arrangements have not been made yet, but I'll probably be going > >back to Maryland almost immediately to attend. > > http://ftp.arl.army.mil/~mike/ping.html
[IFWP] ESI v. ICANN
http://www.icann.org/tlds/correspondence/esi-v-icann-13nov00.htm -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Corporate lobbying stopped .union internet domain (fwd)
-- Forwarded message -- Date: Tue, 21 Nov 2000 15:30:49 + From: Chris Bailey <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Corporate lobbying stopped .union internet domain Press statement by British Trade Union Congress Corporate lobbying stopped .union internet domain The refusal to grant a new .union top level domain to the internet, to join domains such as .com, is not only deeply disappointing but suggests that corporate America now runs the internet, says the TUC today. The Internet Corporation for Assigned Names and Numbers (ICANN) meeting in Los Angeles yesterday granted applications for seven new top level domains including .biz and .museum, but turned down an application from the International Confederation of Free Trade Unions, backed by the TUC, for a union domain. The ICANN staff had recommended support for the .union domain and the proposal had also won the support of the non-commercial internet users meeting in advance of the ICANN. However US employers and intellectual property lawyer groups had opposed the proposal. Nigel Stanley, Head of Campaigns and Communications at the TUC said, "This is a deeply disappointing decision. Given the support of the technical experts and other non-commercial users, it is hard to conclude anything other than this is simple anti-union prejudice stoked up by corporate interests in the US. Dissatisfaction with internet governance can only now grow. However this will not stop unions using the net to promote our message." Notes to Editors: All TUC press releases can be found at www.tuc.org.uk A series of TUC rights leaflets are available on the know your rights line 0870 600 4 882. Lines are open every day from 8am-10pm. Calls are charged at the national rate. Contacts: Media enquiries: Nigel Stanley on 020 7467 1244 or 076 99 755102 (pager) --- You are currently subscribed to ncdnhc-discuss as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
Re: [IFWP] Re: re ICANN Should Approve More Top Level Domains
On Mon, 20 Nov 2000, Michael Sondow wrote: > Joe Baptista wrote: > > > > point, click, reboot - and astalavista ICANN. > > Lo siento, Joe, pero "hasta la vista" no basta. Hace falta que ICANN > desaparece. Estoy en el acuerdo con usted. Pienso que estamos viendo el fin da fiesta de ICANN. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: re ICANN Should Approve More Top Level Domains
I agree with Judith on this. Seeing the entire internet - instead of the ICANN restricted internet is as simple as point click and reboot. Further data is available at www.youcann.org and instructions are located here http://www.youcann.org/instructions.html and include a link to a downloadable program that fixes your dns to see the whole internet. point, click, reboot - and astalavista ICANN. regards joe On Mon, 20 Nov 2000, Judith Oppenheimer wrote: > re ICANN Should Approve More Top Level Domains, > http://www.cluebot.com/article.pl?sid=00/11/20/1714249 > > Great article, but Declan and I have a slightly different take on > his mention of alternative servers, as he states it "... requires > tech-savvy users to reconfigure their computers..." > > This is a seemingly minor point, yet it is so significant, > perpetuating this myth that only the "tech-savvy" can access the > entire Internet. Its counterproductive, and simply not true. > > I cannot figure out any advanced features on my microwave, my > organizer, my cell phone - forget about the VCR ... yet it took > me maybe 3 minutes, tops, to upgrade my computer in order to > access all of the net. > > Hardly a "tech-savvy" process, it was more like point, click and > reboot, resulting in immediate access to .com/.net/.org PLUS > .web/.biz etc. > > I've written Declan and the WSJ editors suggesting that we > dispel, finally, this myth of the hard-to-do, beyond-reach > Internet. Telling readers its just point, click, and reboot, > would go a long way toward poking a canon-ball sized hole in the > ICANN facade. > > Judith > > Judith Oppenheimer, 212 684-7210, 1 800 The Expert > Publisher, http://www.ICBTollFreeNews.com > President, http://www.1800TheExpert.com > FREE 800/Domain Classifieds, http://ICBclassifieds.com > Domain Name & 800 News, Intelligence, Analysis > > > > -Original Message- > > From: Owner-Domain-Policy > > [mailto:[EMAIL PROTECTED]]On Behalf Of Joe > Baptista > > Sent: Monday, November 20, 2000 12:24 PM > > To: [EMAIL PROTECTED] > > Subject: Re: CDR: RE: What got censored today... (fwd) > > > > > > -- Forwarded message -- > > Date: Mon, 20 Nov 2000 13:43:14 -0500 > > From: Declan McCullagh <[EMAIL PROTECTED]> > > To: Joe Baptista <[EMAIL PROTECTED]> > > Cc: "Carskadden, Rush" <[EMAIL PROTECTED]>, > > "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> > > Subject: Re: CDR: RE: What got censored today... (fwd) > > > > I have an op-ed in today's Wall Street Journal that mentions > > alternative > > DNS schemes: > > > > http://www.cluebot.com/article.pl?sid=00/11/20/1714249 (html) > > http://www.politechbot.com/p-01507.html (text) > > > > No response yet from ICANN, Esther Dyson, Vint Cerf, etc. > > > > -Declan > > > > > > > -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] The OpenNIC project Root Sync Report Mon Nov 20 12:48:50 EST 2000
The OpenNIC project Root Sync report for Mon Nov 20 12:48:50 EST 2000 http://www.opennic.unrated.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE <<< add ns MASTER.DNS.BE. to root >>> delete ns NS.DNS.BE. from root >>> delete ns SPARKY.ARL.MIL. from root CA - ERROR detected in zone .CA <<< add ns MERLE.CIRA.CA. to root <<< add ns RS0.NETSOL.COM. to root >>> delete ns RS0.INTERNIC.NET. from root COM - ERROR detected in zone .COM <<< add ns D.GTLD-SERVERS.NET. to root >>> delete ns F.ROOT-SERVERS.NET. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root EC - ERROR detected in zone .EC <<< add ns A.I-DNS.NET. to root <<< add ns B.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns D.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root ES - ERROR detected in zone .ES <<< add ns INECO.NIC.ES. to root <<< add ns MUNNARI.OZ.AU. to root <<< add ns NS1.NIC.ES. to root <<< add ns NS3.NIC.FR. to root >>> delete ns CHICO.REDIRIS.ES. from root >>> delete ns RS0.INTERNIC.NET. from root GR - ERROR detected in zone .GR >>> delete ns SPARKY.ARL.MIL. from root IN - ERROR detected in zone .IN <<< add ns AUTH00.NS.UU.NET. to root <<< add ns AUTH61.NS.UU.NET. to root <<< add ns SS585.NCST.ERNET.IN. to root >>> delete ns NAVEEN.NCST.ERNET.IN. from root >>> delete ns SOOCHAK.NCST.ERNET.IN. from root IS - ERROR detected in zone .IS >>> delete ns SPARKY.ARL.MIL. from root KY - ERROR detected in zone .KY <<< add ns KYNSE01.MESSAGESECURE.COM. to root >>> delete ns DENEB.DOMAINNT.NET. from root LA - ERROR detected in zone .LA <<< add ns A.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns E.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root >>> delete ns AUTH03.NS.UU.NET. from root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root >>> delete ns DNSSEC2.SINGNET.COM.SG. from root >>> delete ns DNSSEC3.SINGNET.COM.SG. from root >>> delete ns NS.RIPE.NET. from root LU - ERROR detected in zone .LU <<< add ns NS5.DNS.LU. to root MG - ERROR detected in zone .MG <<< add ns ANTANA.IRD.MG. to root <<< add ns NS.IRD.FR. to root <<< add ns NS.NIC.MG. to root >>> delete ns ORSTOM.RIO.NET. from root MH - ERROR detected in zone .MH <<< add ns INS1.TOSA.TWTELECOM.NET. to root >>> delete ns NS1.INC.NET. from root MIL - ERROR detected in zone .MIL <<< add ns CON1.NIPR.MIL. to root <<< add ns EUR2.NIPR.MIL. to root <<< add ns PAC2.NIPR.MIL. to root >>> delete ns C.ROOT-SERVERS.NET. from root >>> delete ns D.ROOT-SERVERS.NET. from root >>> delete ns F.ROOT-SERVERS.NET. from root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root NET - ERROR detected in zone .NET <<< add ns D.GTLD-SERVERS.NET. to root >>> delete ns F.ROOT-SERVERS.NET. from root NL - ERROR detected in zone .NL <<< add ns NS2.DOMAIN-REGISTRY.NL. to root >>> delete ns SPARKY.ARL.MIL. from root NP - ERROR detected in zone .NP <<< add ns NS.APNIC.NET. to root <<< add ns SHIKHAR.MOS.COM.NP. to root >>> delete ns TRF.NIC.AD.JP. from root NZ - ERROR detected in zone .NZ <<< add ns NS1.DNS.NET.NZ. to root >>> delete ns NS1.WAIKATO.AC.NZ. from root ORG - ERROR detected in zone .ORG <<< add ns D.GTLD-SERVERS.NET. to root >>> delete ns F.ROOT-SERVERS.NET. from root QA - ERROR detected in zone .QA <<< add ns NS1.QATAR.NET.QA. to root <<< add ns NS3.QATAR.NET.QA. to root >>> delete ns NS1.DOHA.NET. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root SK - ERROR detected in zone .SK <<< add ns NS.TELECOM.SK. to root SR - ERROR detected in zone .SR <<< add ns NS1.NL.CONCENTRIC.COM. to root >>> delete ns NS1.NL.GXN.NET. from root TV - ERROR detected in zone .TV <<< add ns NS4.NIC.TV. to root <<< add ns UDNS1.ULTRADNS.NET. to root <<< add ns UDNS2.ULTRADNS.NET. to root US - ERROR detected in zone .US <<< add ns RS0.NETSOL.COM. to root >>> delete ns RS0.INTERNIC.NET. from root UZ - ERROR detected in zone .UZ <<< add ns NS.UZ. to root VA - ERROR detected in zone .VA <<< add ns DNS.NIC.IT. to root >>> delete ns NS.PIPEX.NET. from root >>> delete ns NS0.PIPEX.NET. from root >>> delete ns NS1.PIPEX.NET. from root VN - ERROR detected in zone .VN <<< add ns NS1.GIP.NET. to root <<< add ns NS2.GIP.NET. to root >>> delete ns NS.UU.NET. from root >>> delete ns SUNIC.SUNET.SE. from root
[IFWP] Re: CDR: RE: What got censored today... (fwd)
-- Forwarded message -- Date: Mon, 20 Nov 2000 13:43:14 -0500 From: Declan McCullagh <[EMAIL PROTECTED]> To: Joe Baptista <[EMAIL PROTECTED]> Cc: "Carskadden, Rush" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> Subject: Re: CDR: RE: What got censored today... (fwd) I have an op-ed in today's Wall Street Journal that mentions alternative DNS schemes: http://www.cluebot.com/article.pl?sid=00/11/20/1714249 (html) http://www.politechbot.com/p-01507.html (text) No response yet from ICANN, Esther Dyson, Vint Cerf, etc. -Declan On Fri, Nov 17, 2000 at 12:30:50PM -0500, Joe Baptista wrote: > On Fri, 17 Nov 2000, Carskadden, Rush wrote: > > > I can't read it very well. What does it say? > > It's a little sign that says "USE ORSC DNS" or something like that - see > www.yourcann.org for more data. > > Joe > > > > > ok, > > Rush > > > > > > -Original Message- > > From: Jim Choate [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, November 16, 2000 9:43 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: What got censored today... (fwd) > > > > > > > > > > > > > > > > He is able who thinks he is able. > > > >Buddha > > > >The Armadillo Group ,::;::-. James Choate > >Austin, Tx /:'/ ``::>/|/ [EMAIL PROTECTED] > >www.ssz.com.', `/( e\ 512-451-7087 > >-~~mm-'`-```-mm --'- > > > > > > -- Forwarded message -- > > Date: Thu, 16 Nov 2000 19:27:13 -0800 > > From: Simon Higgs <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > Subject: What got censored today... > > > > > > > > http://cyber.law.harvard.edu/scripts/rammaker.asp?s=cyber&dir=icann&file=ica > > nn-111600&start=0-09-04 > > > > Starts at 2:18:20 > > > > Lasts about five seconds before Mr Anal-Retentive-Bald-Video-Guy censors it. > > > > > > -- > Joe Baptista > > http://www.dot.god/ > dot.GOD Hostmaster > +1 (805) 753-8697 >
[IFWP] The Internet Namespace Cooperative Root Sync Report Mon Nov 20 05:34:39 EST 2000
The Internet Namespace Cooperative Root Sync report for Mon Nov 20 05:34:39 EST 2000 http://www.tinc-org.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ ES - ERROR detected in zone .ES <<< add ns INECO.NIC.ES. to root <<< add ns MUNNARI.OZ.AU. to root <<< add ns NS1.NIC.ES. to root <<< add ns NS3.NIC.FR. to root >>> delete ns CHICO.REDIRIS.ES. from root >>> delete ns RS0.INTERNIC.NET. from root KY - ERROR detected in zone .KY <<< add ns KYNSE01.MESSAGESECURE.COM. to root >>> delete ns DENEB.DOMAINNT.NET. from root MH - ERROR detected in zone .MH <<< add ns INS1.TOSA.TWTELECOM.NET. to root >>> delete ns NS1.INC.NET. from root
[IFWP] i-DNS.net International Root Sync Report Mon Nov 20 05:30:00 EST 2000
i-DNS.net International Root Sync report for Mon Nov 20 05:30:00 EST 2000 http://www.i-DNS.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE >>> delete ns NS.DNS.BE. from root CA - WARNING tld lookup on IDNS rootserver 208.184.174.7 FAILED DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root EC - ERROR detected in zone .EC <<< add ns A.I-DNS.NET. to root <<< add ns B.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns D.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root ES - ERROR detected in zone .ES <<< add ns INECO.NIC.ES. to root <<< add ns MUNNARI.OZ.AU. to root <<< add ns NS1.NIC.ES. to root <<< add ns NS3.NIC.FR. to root >>> delete ns CHICO.REDIRIS.ES. from root >>> delete ns RS0.INTERNIC.NET. from root FI - WARNING tld lookup on IDNS rootserver 208.184.174.7 FAILED FR - WARNING tld lookup on IDNS rootserver 208.184.174.7 FAILED KY - ERROR detected in zone .KY <<< add ns KYNSE01.MESSAGESECURE.COM. to root >>> delete ns DENEB.DOMAINNT.NET. from root LA - ERROR detected in zone .LA >>> delete ns B.I-DNS.NET. from root >>> delete ns D.I-DNS.NET. from root MH - ERROR detected in zone .MH <<< add ns INS1.TOSA.TWTELECOM.NET. to root >>> delete ns NS1.INC.NET. from root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root
[IFWP] Highlights of the ICANN meeting (fwd)
Aurbach on "How I would decide TLDS if I were seated" Sexton on ".XXX" Peter Dengate Thrush: "We (cctlds) may look for other root servers" http://cyber.law.harvard.edu/scripts/rammaker.asp?s=cyber&dir=icann&file=icann-111500&start=10-31-32
[IFWP] Our resident Fraud Rick Harris continues ticking
Now he's claiming ICANN has given it's blessing to his dot.pod tlds. Obviously I'm going to have to respond to his claim and set people straigh. The man has yet to return to me the non-disclosure agreement and that's not nice. Anyway - more marketing bull from our resident fraud. Regards Joe -- Forwarded message -- Date: Fri, 17 Nov 2000 15:43:16 -0500 From: Frederick Harris <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: ISP Investors wanted for Cyber I.D. -The Next Wave in Domain Name Services HERE COMES THE NEXT WAVE IN DOMAIN NAMES The "Cyber I.D." description which follows in this memo is intended for every ISP in the U.S. and Canada. Following yesterday's decision by ICANN to include seven new TLDs in the DNS root including "info", "biz", "museum", "aero" , "coop", "pro" and "name" - it has become clear that "personal online domains" or "pods" - and the hosting of those name spaces by ISPs - is a future trend for the world wide web. In other words "Cyber I.D." is an idea whose time has come. (See www.icann.org) By giving its blessing for a new top-level domain (TLD) called "name" - ICANN has implicitly validated the *concept* of "Cyber I.D." and "personal online domains" or "pods". PODS will become available to any ISP that wants to sell and host them as soon as possible after January 1, 2001. Each participating ISP will function as an accredited "registry" for "Cyber I.D." and will also be able to sell and host one or more in the network of 500 dot com master addresses that are layered under the "personal online domains". The distinction between "pods" and the TLDs sanctioned by ICANN is of course that all dot pods perfectly resolve inside the root zone of the global internet - without permission from ICANN - and there is nothing to pay to Network Solutions (NSI) *because* "pods" are layered over a large thematic network of 500 dot com (.com) name spaces. Investment and affiliate inquiries are invited from ISPs and other investors on letterhead only please and should be FAXED TO IDEXIS CORPORATION at 905-729-0966. "Pods" will sell to domain name registrants for $5.00 each per year - in other words one dollar *less* than the wholesale rate charged by NSI to ICANN-accredited registrars - and $ 5.00 less that the best rate presently offered to affiliates from OpenSRS. This is a wonderful opportunity for ISPs and individuals who are interested in investing in - or becoming affiliated with - "Cyber I.D." The details follow. Email Privacy Policy Idexis does not send unwarranted or unwanted email. Idexis respects your privacy. Please reply with the word "cancel" in the subject line of your email utility or browser if you do not intend to receive further information about Idexis Corporation. " Simplification [means] to eliminate the unnecessary so that the necessary may speak". Hans Hoffman Abstract Expressionist CYBER I.D. EXPLAINED Idexis Corporation, which is a Delaware company and an Ontario company is a web startup that has devised a web commerce model called Cyber I.D.(tm). The purpose of Cyber I.D. (please see the trademarks for Idexis and Cyber I.D. at ) is to develop a web architecture that uses a large network of existing dot com address as the platform for "personal online domains" or "pods". In essence the Futurepod model makes it feasible for television stations, television networks,newspapers, magazines and in fact all other content producers - large and small, including small businesses - to reach stratified and segmented audiences of viewers, listeners and readers through personal online domains or "pods" on the public internet. In other words there is a huge untapped market for personal online domains. And ICANN has recognized that fact by approving a new TLD called ".name". The significance of "personal online domains" as a business concept stems from the fact that whereas the public internet as a device for web commerce appears to first and foremost require successful business models (and therefore recognizable web sites with significant brand awareness - i.e., a Yahoo or an Amazon.com) - "personal online domains" or "pods" allow any ISP, retailer, merchandiser, advertiser or even the smallest commercial enterprise to reach directly into the homes of audiences of persons, each of whom has been assigned a proprietary and personal "dot com" address - which is also a "pod" or name space on the public internet. This idea - that each and every "owner" of a "pod" is at the same time the proprietor of a dot com name space on the public internet - is key. In other words - whereas the conventional broadcasting and newspapering model for mass media diffusion is "one source to many receivers" - which is a web commerce model - the Futurepod model in effect stand
[IFWP] TINC Policy
http://www.tinc-org.com/ - good rules - maybe ICANN should review them. TINC Rules & Guidelines Social Rules Technical Rules Guidelines Social Rules 1.No more than one top level domain allocated to an individual person or organization. This is to prevent land grabs, and immediate flattening of the name space. 2.A maximum of 15 top level domains to be added to the current top level domains. 3.A maximum of 2 top level domains added per year. 4.Exceptions to 1, 2, and 3 may be made for certain specific reasons, subject to unanimous veto of the TINC steering committee: a.Infrastructure. Common infrastructure is important. Domain names created by the IETF, IANA, and their successors need to be uniformly visible from all sites. TINC will track and include any domains created by these bodies. b.Public good. Coherent collections of domains that require coordinated management should be maintained by a single registrar. The steering committee will implement the following mechanisms: 1.Direct appeal to the members of TINC by majority of TINC registrars. 2.Simply majority vote of Committee members. c.Popular demand via major network service providers Any domain requested by 10 or more major ISPs or companies owning the equivalent of a class B address space or greater shall be included in the TINC root. 5.No top level domain names may conflict with current top level domains, even if those top level domains are not recognized by TINC. A "top level domain" is one that has currently functional name service at a level at least meeting the technical criteria for TINC-root domains set out below. 6.This is a non-profit effort. Charges for top level domains will be minimal, if any. 7.Running of the additional top level domains is completely the concern of the organization who created that top level domain. TINC is only concerned that the name servers for that TLD are reachable and technically sound. Technical Rules 1.For any top level domain, there must be at least two network-distant name servers running at all times. Network distant is defined as at least the last 4 hops differing in a traceroute to the servers from the TINC core at ies-energy.com. These servers must also reside in separate physical facilities to prevent outages caused by power failure, flood or similar disaster. 2.The name servers running the top level domain must not be succeptible to any known security problems, such as cache corruption/poisoning and be kept current with regard to such problems, at least to the best-practice levels available from the most current, freely distributable software. 3.The name servers running the top level domain must be reasonably compliant with the current rfc's related to DNS. Guidelines 1.It is recommended that servers for top level domains run a current version of BIND, or a similar, current, name server. In practical terms, the technical rules more or less require doing so. 2.TLD's should have at least three servers, at network and geographic distance from each other. This will help prevent all your second level domains from disappearing if your network link or name server dies. In any event, while the technical rules require two network-distant servers in separate facilities, the third, separate and geographically distant server is strongly recommended. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] multilingual domain names (fwd)
documentation and resources related to the new multilingual domain names: http://gsa.secret.org/i18n/ kind regards philippe Philippe Landau <[EMAIL PROTECTED]>
[IFWP] IEFT draft changing the dns to serve TM interests
--- begin forwarded text Date: Wed, 14 Nov 2000 06:44:00 -0500 (EST) To: ietf-announce: ; Subject: I-D ACTION:draft-klensin-dns-role-00.txt From: [EMAIL PROTECTED] A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Role of the Domain Name System Author(s) : J. Klensin Filename: draft-klensin-dns-role-00.txt Pages : 10 Date: 13-Nov-00 The original function and purpose of the DNS is reviewed, and contrasted with some of the functions into which it is being forced today and some of the newer demands being placed upon it or suggested for it. A framework for an alternative to placing these additional stresses on the DNS is then outlined. This document and that framework are not a proposed solution, only a strong suggestion that the time has come to begin thinking more broadly about the problems we are encountering and possible approaches to solving them. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-klensin-dns-role-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-klensin-dns-role-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: [EMAIL PROTECTED] In the body type: "FILE /internet-drafts/draft-klensin-dns-role-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <[EMAIL PROTECTED]> ENCODING mime FILE /internet-drafts/draft-klensin-dns-role-00.txt <ftp://ftp.ietf.org/internet-drafts/draft-klensin-dns-role-00.txt> --- end forwarded text Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] ietf Internet Draft in RFC 1591
An attempt to justify ICANN control of TLD's and rewrite the rules of RFC 1591 first come - first served provisions. --- begin forwarded text Date: Wed, 14 Nov 2000 06:44:00 -0500 (EST) To: ietf-announce: ; Subject: I-D ACTION:draft-klensin-1591-reflections-01.txt From: [EMAIL PROTECTED] A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Reflections on the DNS, RFC 1591, and Categories of Domains Author(s) : J. Klensin Filename: draft-klensin-1591-reflections-01.txt Pages : 7 Date: 13-Nov-00 RFC 1591,'Domain Name System Structure and Delegation' [1] laid out the basic administrative design and principles for the allocation and administration of domains, from the top level down. It was written before the introduction of the world wide web and rapid growth of the Internet put significant market, social, and political pressure on domain name allocations. In recent years, 1591 has been cited by all sides in various debates, and attempts have been made by various bodies to update it or adjust its provisions, sometimes under pressures that have arguably produced policies that are less well thought out than the original. Some of those efforts have begun from misconceptions about the provisions of 1591 or the motivation for those provisions. This memo includes some thoughts about how 1591 might be interpreted and adjusted by the IANA and ICANN to better reflect today's world while retaining characteristics and policies that have proven to be effective in supporting Internet growth and stability. A variation on this memo has been submitted to ICANN as a comment on its evolving TLD policies. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-klensin-1591-reflections-01.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-klensin-1591-reflections-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: [EMAIL PROTECTED] In the body type: "FILE /internet-drafts/draft-klensin-1591-reflections-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <[EMAIL PROTECTED]> ENCODING mime FILE /internet-drafts/draft-klensin-1591-reflections-01.txt <ftp://ftp.ietf.org/internet-drafts/draft-klensin-1591-reflections-01.txt> --- end forwarded text Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] one last dance with vixie - CERT Advisory CA-2000-20
Here we go again folks - yes another bind vulnerability. will this be vixies last dance - or what. joe -- Forwarded message -- Date: Mon, 13 Nov 2000 17:24:17 -0500 (EST) From: CERT Advisory <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: CERT Advisory CA-2000-20 -BEGIN PGP SIGNED MESSAGE- CERT Advisory CA-2000-20 Mulitple Denial-of-Service Problems in ISC BIND Original release date: November 13, 2000 Source: CERT/CC A complete revision history is at the end of this file. Systems Affected * Systems running Internet Software Consortium (ISC) BIND version 8.2 through 8.2.2-P6 * Systems running name servers derived from BIND version 8.2 through 8.2.2-P6 Overview The CERT Coordination Center has recently learned of two serious denial-of-service vulnerabilities in the Internet Software Consortium's (ISC) BIND software. The first vulnerability is referred to by the ISC as the "zxfr bug" and affects ISC BIND version 8.2.2, patch levels 1 through 6. The second vulnerability, the "srv bug", affects ISC BIND versions 8.2 through 8.2.2-P6. Derivatives of the above code sets should also be presumed vulnerable unless proven otherwise. I. Description The Internet Software Consortium, the maintainer of BIND, the software used to provide domain name resolution services, has recently posted information about several denial-of-service vulnerabilities. If exploited, any of these vulnerabilities could allow remote intruders to cause site DNS services to be stopped. For more information about these vulnerabilities and others, please see http://www.isc.org/products/BIND/bind-security.html Two vulnerabilities in particular have been categorized by both the ISC and the CERT/CC as being serious. The "zxfr bug" Using this vulnerability, attackers on sites which are permitted to request zone transfers can force the named daemon running on vulnerable DNS servers to crash, disrupting name resolution service until the named daemon is restarted. The only preconditions for this attack to succeed is that a compressed zone transfer (ZXFR) request be made from a site allowed to make any zone transfer request (not just ZXFR), and that a subsequent name service query of an authoritative and non-cached record be made. The time between the attack and the crash of named may vary from system to system. This vulnerability has been discussed in public forums. The ISC has confirmed that all platforms running version 8.2.2 of the BIND software prior to patch level 7 are vulnerable to this attack. The "srv bug" This vulnerability can cause affected DNS servers running named to go into an infinite loop, thus preventing further name requests to be handled. This can happen if an SRV record (defined in RFC2782) is sent to the vulnerable server. Microsoft's Windows 2000 Active Directory service makes extensive use of SRV records and is reportedly capable of triggering this bug in the course of normal operations. This is not, however, a vulnerability in Microsoft Active Directory. Any network client capable of sending SRV records to vulnerable name server systems can exercise this vulnerability. The CERT/CC has not received any direct reports of either of these vulnerabilities being exploited to date. Both vulnerabilities can be used by malicious users to break the DNS services being offered at all exposed sites on the Internet. System administrators are strongly recommended to upgrade their DNS software with either ISC's current distribution or their vendor-supplied software. See the Solution and Vendor Information sections of this document for more details. II. Impact Domain name resolution services (DNS) can be disabled on affected servers from arbitrary remote hosts. III. Solution Apply a patch from your vendor The CERT/CC recommends that all users of ISC BIND upgrade to the recently-released BIND 8.2.2-P7, which patches both of the vulnerabilities discussed in this document. Sites running vendor-specific distributions of domain name resolution software should check the Vendor Information section below for more specific information on how to upgrade to non-vulnerable software. Restrict zone transfers to trusted hosts If it is not possible to immediately upgrade systems affected by the "zxfr bug", the ISC suggests not allowing zone transfers from untrusted hosts. This action, however, will not mitigate against the effects of an attack using the "srv bug". Although it has been reported that not allowing recursive queries may help mitigate against the "zxfr" vulnerability, ISC has indicated that this is not the case. Appendix A. Vendor Information The Internet Software Consortium
[IFWP] The Internet Namespace Cooperative Root Sync Report Mon Nov 13 05:35:01 EST 2000
The Internet Namespace Cooperative Root Sync report for Mon Nov 13 05:35:01 EST 2000 http://www.tinc-org.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ ES - ERROR detected in zone .ES <<< add ns INECO.NIC.ES. to root <<< add ns MUNNARI.OZ.AU. to root <<< add ns NS1.NIC.ES. to root <<< add ns NS3.NIC.FR. to root >>> delete ns CHICO.REDIRIS.ES. from root >>> delete ns RS0.INTERNIC.NET. from root KY - ERROR detected in zone .KY <<< add ns KYNSE01.MESSAGESECURE.COM. to root >>> delete ns DENEB.DOMAINNT.NET. from root
[IFWP] i-DNS.net International Root Sync Report Mon Nov 13 05:30:00 EST 2000
i-DNS.net International Root Sync report for Mon Nov 13 05:30:00 EST 2000 http://www.i-DNS.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE >>> delete ns NS.DNS.BE. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root EC - ERROR detected in zone .EC <<< add ns A.I-DNS.NET. to root <<< add ns B.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns D.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root ES - ERROR detected in zone .ES <<< add ns INECO.NIC.ES. to root <<< add ns MUNNARI.OZ.AU. to root <<< add ns NS1.NIC.ES. to root <<< add ns NS3.NIC.FR. to root >>> delete ns CHICO.REDIRIS.ES. from root >>> delete ns RS0.INTERNIC.NET. from root KY - ERROR detected in zone .KY <<< add ns KYNSE01.MESSAGESECURE.COM. to root >>> delete ns DENEB.DOMAINNT.NET. from root LA - ERROR detected in zone .LA >>> delete ns B.I-DNS.NET. from root >>> delete ns D.I-DNS.NET. from root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root
[IFWP] Re: Reply re: dates (fwd)
On Mon, 13 Nov 2000, William X. Walsh wrote: > Hello Joe, > > Monday, November 13, 2000, 12:58:51 AM, you wrote: > > > more pleadings for an audience .. > > Hmm, as much as I detest Joe's methods, I have to say that I received > several email from Mr Harris as well, asking to talk to me via phone > many times about his "proposals." I finally had to make it perfectly > clear and spell it out that I was not interested in discussing his > plans, and that they made absolutely no sense whatsoever before he > stopped. Don't forget the ass kissing. I swear the man is the biggest brown noser I ever came across. I would answer my phone and end up getting a litany of ass kissing platitudes as to how great I am. Ass kissing don't work with me - it annoys me. If I need my ass kissed I use my little black book. > In light of that, I believe Joe is telling the truth here, and that Mr > Harris is trying to deny things that he has actually become so well > known for. Joe always tells the truth. I think that's well known by now. Harris is known by almost all the major admins in the loop. What we have here is a wheeler dealer who wants to sell his way into heaven. Do you believe he actually offered me to run this ICANN business. He actually thought I'd find value in it. And I still don't know what an eTLD is. Maybe someday Mr. harris can take us all to lunch and we'll all find out together. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] Joe -Urgent - please read. (fwd)
ass licking and a failed attemt to identify with the target - i.e. yours trully. But in the end - how does an eTLD resolve .. only in the imagination of friderick harris ... -- Forwarded message -- Date: Fri, 15 Sep 2000 08:28:48 -0400 From: Frederick Harris <[EMAIL PROTECTED]> To: Joe Baptista <[EMAIL PROTECTED]> Subject: Joe -Urgent - please read. Dear Joe, Thank you for your memo. I have to respect your wishes, and I do. For that reason I intend to share with you something I share with very few persons. Perhaps this will surprise you, but I am (in a way) somewhat like you are, or say you are. I am a very shy person. I work alone. I struggle mightily each time I do a business trip or a deal with venal capitalists precisely because I prefer quiet and solitude. When you and I last agreed to meet together, I drove all the way up to Huntsville with my wife - and started down the highway toward Ottawa. I then stopped, turned around and came home. I suppose I intuitively understood that it would be a mistake to visit you unannounced - even though I know we will get along terrific. Joseph - the web is ultimately about human connectivity. It isn't about business or profits or corporations or anything of the sort. If you want to discouver the *real* source of the web (in my view) please, look to Pierre Teilhard de Chardin, a Jesuit theologian, who wrote about the internet (he then referred to it as the noosphere) - in 1946 I believe. You can find it in "The Phenomenon of Man" P. Teilhard de Chardin (I forget the name of the publisher). It is not for nothing that I have approached you. I realized some time ago that you are (apparently) reclusive. But I also appreciate your apparent genius and I think you have much to contribute to the entire internet. I don't buy any of this stuff about Ester Polyester - and ICANN - and I could care less about ICANN. I know how to bypass ICANN. . Now - what I suspect that God has given you is a deep understanding of "human connectivity" and the implications of what that means for human beings in the realm of technology. I already know that you are probably very gifted man. It is important, therefore, not only to me but to others - and the internet - that the synergy which I know is there be allowed to happen. I am not going to dwell on that part of it here. So please here me out! I am about as easy going a person as you will find. I would like you to please copnside the following - which are your own words from your memo to me last night: Joe: " The only thing I can offer you is to co-ordinate your admins in setting up the service." Okay! I accept your offer! The papers and money $3,000.00 will go out to CIRA today for the .CA registry. I intend to vigorously compete with all the platers in that name space. I will be doiung it, as I told you, in Canada *and* in California, through Valley Corporation, a company I have set up to sell .CA web addresses in the area that runs rougly along the ,ines of the San Andreas Fault from Silicon Valley down through Southern California into The San Fernando Valley. I will pay you for your admin services. Here is what is required from the privacy of your home and in whatever manner you choose to do it. All I ask is that you please follow through. I will Fedex copies of the Idexis application to you. Your job, if you accept it, will be to "ccordinate all the admins" with CIRA up to the point where CIRA approves the Idexis application. I will then form a busines sparnershiup with another company. You can be the grey eminence who fatherly (if you prefer) sees to it that all the administrative and tecnhnical matters are taken care of so we can have the registy up and running by November 1. I will phne you this morning about this. I will respect your need for privacy. I certainly dfo want to meet with you. But I will do it on your terms. I will phone you in a while. Cheers and God bless! Rick Harris Tel: 905-729-4994
[IFWP] Reply re: dates (fwd)
more pleadings for an audience .. -- Forwarded message -- Date: Wed, 2 Aug 2000 20:37:58 -0400 From: Frederick Harris <[EMAIL PROTECTED]> To: !Dr. Joe Baptista <[EMAIL PROTECTED]> Subject: Reply re: dates Hi Joe, Thanks for getting back to me. I phoned you this morning, but there was no answer at your place. My wife, Merilyn, and I are going to take three days and drive up through Angonquin Park, into Peterborough and on to Ottawa. We leave Tuesday morning. So Wednesday, perhaps for lunch, would be the absolute best time for me. I mentioned that Metilyn would go shopping and, perhaps, you and I can get together over a long luinch and talk about equivalent TLDs and other interesting things. I do hope you will be available. Would you phone me to confirm? Or at any rate reply ASAP? Thanks muchly. Cheers, Rick Tel: 905-729-4994 ++
[IFWP] Re: Reply: The "idea" of the absolute "power" of ICANN is a myth.(fwd)
confusion .. ? -- Forwarded message -- Date: Thu, 17 Aug 2000 14:25:09 -0400 (EDT) From: Joe Baptista <[EMAIL PROTECTED]> To: Frederick Harris <[EMAIL PROTECTED]> Subject: Re: Reply: The "idea" of the absolute "power" of ICANN is a myth. Fred - the internet if simple enough - if you want us to use it - explain it. It's not a lunch thing. Don't try to convence me - convence them. And if they understand so will I. So far all I've seen is marketing and I still have no understanding of it. This is not an invitation for you to explain it to me. Explain it to the group - they are the ones who count. regards Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697 On Thu, 17 Aug 2000, Frederick Harris wrote: > Hello Joseph, > I offered to visit with you and tell you how the eTLDs > work. If I rightly understood your reply, you did not wish to meet with me. The > offer is still open. I'm not going to disclose to this list how the eTLDs work. > Why don't you phone me? > Tel: 905-729-4994 > Cheers, R. > > "!Dr. Joe Baptista" wrote: > > > Ross at tucows recntly told me that clarity is a part of zen. Maybe we > > should all do some zen. > > > > Rick - everyone here who is without a technical clue has no idea what your > > going on about - simply put those of us with a clue have no idea what your > > going on about. > > > > Could you simply provide the name of an eTLD (or domains) and tell us the > > proceedure for finding it. Becaue have no idea what your talking > > about and the only way we can evaluate this is with technical > > documentation or examples. > > > > regards > > Joe Baptista > > > > http://www.dot.god/ > > dot.GOD Hostmaster > > +1 (805) 753-8697 > > On Thu, 17 Aug 2000, Rick Harris wrote: > > > > > Reply to Michael Sondow: > > > The "Power" of ICANN is a Myth > > > > > > Michael, > > > Others long ago figured out how to bypass > > > ICANN by devising "equivalent tlds" (eTLDS). Etlds > > > resolve inside the root zone architecture of the public > > > internet. In other words, unlike ORSC - which > > > (understandably and rightly) seeks to build the equivalent of a second > > > railway track to offset the monopsony power of ICANN- > > > the actual source of ICANN's power which is > > > monopolization of the "legitimized" root of the DNS, has disappeared with > > > the invention of eTLDs. > > > > > > Apparently the digerati on the DNS Policy List prefer to ignore > > > eTLDs - which is fine. People if they prefer can waste their time and > > > political capital complaining about ICANN procedural > > > matters when ICANN effectively has no further power over > > > the DNS. For that reason - power - ICANN insists on the single-root > > > architecture. However, eTLDs are impervious to ICANN *because* (unlike > > > ORSC) they take the path of least resistance which - in terms of global > > > connectivity - happens to reside for the present *inside* the root. > > > > > > Any physics major, organizational specialist or student of systems theory > > > will tell you the same thing. Innovation (good and bad) always takes the > > > path of least resistance. > > > > > > That being said, the plain fact of the matter is that there is nothing > > > complicated about eTLDs - and they do not require $50,000 to create one. It > > > baffles me that your correspondents on the list do not seem to have grasped > > > that very simple fact. There seems to be a disconnect between the imagined > > > power of ICANN and the reality of the fact that eTLDs effectively make ICANN > > > a political non sequitur. This doesn't defeat the legitimate *technical* > > > argument that having two parallel DNSs might tend to introduce > > > turbulence in the system. But turbulence will happen if - and only if - the > > > two "competitive" systems seek to create universal connectivity from a > > > "single source" or root. > > > > > > The fallcy of the argument that a duality inside the root is a good idea > > > contradicts common sense because any reasonable person understands that more > > > than one *singularity* insi
[IFWP] ICANN - Independent Auditors' Report
"We were unable to obtain sufficient verifiable evidence supporting certain Country Code Top Level Domain (ccTLD) accounts receivable totaling $1,355,000 at June 30, 2000 or the related registry fee revenue, which is included in the change in net assets for the year then ended as described in note 2 to the financial statements; nor were we able to satisfy ourselves as to the adequacy of the allowance for doubtful accounts related to these receivables." KPMG http://www.icann.org/financials/financial-report-fye-30jun00-letter.htm -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] RE: Your on the list ;-)
> Congrats .. looks like your on the list. Now my question is why is >that?? well, I'll be damned. beatsa hell outta me! of course, Esther has been a Loyal EGR Irregular in Good Standing from Jump Street. maybe she stuck me on there. or John Patrick at IBM, whom I used to work with in that illustrious organization (though the latter explanation is highly unlikely). thanks for sending. it's yet another mystery wrapped in an enigma. sorta like a cognitive fajita.
[IFWP] Re: Your on the list ;-)
I think I know why. This is an ancient list. Toru and Eric Jensen are on it too. They don't have those email addresses any more. Some one got this from an ancient distribution list. Who knows where.
[IFWP] Re: ICBTollFreeNews.Com HEADS UP HEADLINES
Hi: The information in your article is incorrect regarding registrar.com. As of yesturday there were 3,072 multilingual domains registered using the RACE encoding method i.e. bq-- as a prefix. Of these only 466 were registered by register.com. Not thousands. At best INNERWISE is the leader in registrations. >14 DOMAINPEOPLE, INC. > 161 DOTSTER, INC. > 1 HANGANG SYSTEMS, INC. D/B/A DOREGI.COM > 2 IHOLDINGS.COM, INC. D/B/A DOTREGISTRAR.COM > 1,796 INNERWISE, INC. D/B/A ITSYOURDOMAIN.COM > 158 MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE > 124 NETWORK SOLUTIONS, INC. > 466 REGISTER.COM, INC. >18 SPEEDNAMES, INC. > 331 TUCOWS.COM, INC. > = > 3,072 TOTAL On Thu, 9 Nov 2000 [EMAIL PROTECTED] wrote: > F - MULTILINGUAL DOMAIN DEPLOYMENT IS PREMATURE > The Internet Society 'believes the commercial test bed is premature under > the technical standards of the Internet' - Verisign moves forward. ICANN > denounces pre-registration of domain names - Register.com pre-registers > thousands of multilingual names. Beijing has lodged a complaint with the > ICANN over the registration of Chinese domain names - ICANN rides > Verisign's 'progress' coat-tails, implies Internet Society coordination, > claims multilingual domains could bring 'very significant changes to the > way the DNS can be used.' Messy messy messy. > CONTINUED HERE: http://www.icbtollfree.com/article.cfm?articleId=4742 -- Joe Baptista http://www.dot.god/
[IFWP] FYI - stats on Multiligual domain names (fwd)
-- Forwarded message -- Date: Wed, 8 Nov 2000 12:50:17 -0500 (EST) From: !Dr. Joe Baptista <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: FYI - stats on Multiligual domain names Some time ago people here expressed concerns that there were many preregistrations of domains starting with the BQ-- string. Yes - people have been registering domains. According to draft-ietf-idn-race-02.txt there were no domains starting with the string "BQ--" registered on or about August 2000. I obtained a complete list of these domains from the whois and can verify that indeed the "BQ--" string has recently experienced some popularity. To date there are 3,072 domain names which use RACE (Row-based ASCII Compatible Encoding) for Internationalized Domain Names. The leading registrar is INNERWISE with 1,796 registered domains. 14 DOMAINPEOPLE, INC. 161 DOTSTER, INC. 1 HANGANG SYSTEMS, INC. D/B/A DOREGI.COM 2 IHOLDINGS.COM, INC. D/B/A DOTREGISTRAR.COM 1,796 INNERWISE, INC. D/B/A ITSYOURDOMAIN.COM 158 MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE 124 NETWORK SOLUTIONS, INC. 466 REGISTER.COM, INC. 18 SPEEDNAMES, INC. 331 TUCOWS.COM, INC. = 3,072 TOTAL regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] the funniest root server soa i ever seen
dig @62.0.46.212 . soa or dig @62.0.46.213 . soa I would say the above two make the fashion statement of the dns world as the funniest root server soa ever. I like people who have a sense of the abusrd. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] new root servers - a la surf and turf
sites running their own root servers. http://www.open-nic.org/ http://www.council.net/ http://www.idenny.com/ http://www.livingnexus.com/ http://surpass.gcis.net/ http://www.interliant.com/main/ilv6.nsf/public/home http://www.houdat.net/ http://www.domains.com/ http://www.eenet.com.tw/eenet/index.asp http://www.crownintl.com/crownintl/ http://www.teambyron.com/ http://www.edusystem.co.kr/ http://www.nortel.com/ http://www.nd.edu/ http://www.new-scotland.com/ and so on and so forth ... over 221 roots found todate. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Root server list update (fwd)
I'm so exceited. Those non USG roots just keep growing. Here's the latest list. A.ROOT-SERVERS.ORSC. A.ROOT-SERVERS.NET. NS.INTERLIANT.COM. NS1.FUTUREQUEST.NET. TINC-ORG.COM. REALNAME. SYS01.INAME.NET. NS1.DOMAINS.COM. RS2.AURSC.AH.NET. HOME.KASHPUREFF.ORG. EUGENE.KASHPUREFF.ORG. A.I-DNS.NET. KVINSLAND.SKPTE.ORG. KAPPA.CROWNINTL.COM. NS1.WWW.HOUDAT.NET. SERVER.TEAMBYRON.COM. BANSHEE.MYBIS.COM. 3TY.BROADI.COM. NS1.WERCS.COM. NS1.ROOT.OPENNIC. WWW.EDUSYSTEM.CO.KR. YANC001FS.YPC.COM. ADMINW2K.NS1.MROUTLAW.COM. ADS.DPIDVAR.COM. NS1.DNSUSA.ORG. RIONEGRO.RIONEGRO.CUBOSOFT.NET. ALEXA.IOGLYPHIX.NET. MEGABYTE.ALIVENEWMEDIA.MB.CA. ARGUS.AMHERST.KILLERWEBSITE.COM. SERVER3.TCCF.NET. DATARAD.DATARAD.INTRA. PROCSY.PROCSYS.KWANGWOON.AC.KR. SCIRONSRV.SCIRON.SCIRON.SE. KEG-DEPOT.DDA.DDAONLINE.COM. NS.CNSOFT.DE. CNA-GDWI-0.CNA.AT. NCR.ND.EDU. DOMAINSRVR.GRINNELL.EDU. BMERH365.CA.NORTEL.COM. EENETSVR.EENET.COM.TW. BLACKBOX.75CONCORD.75CONCORD.COM. CEREBUS.NEW-SCOTLAND.COM. MCIS01. UA1.REDDEERNET.COM. JTAIME.NET. NT2000. SERVER.DONE-THAT.COM. IWHSERVER.IWH.COM. COLONEL-HATHI.KO-NP.DE. JULIET.EBIZS.NET. ROMEO.EBIZS.NET. JASMINE.RPPIA.COM. NT.W2K.POLEIS.NET. ALPHA.WAYGEE.COM. DMAXNTPDC01.DMAXUSFLTAM. NET1.HOME.WIN2KTECH.COM. WWW.WALDENS.COM. MERLIN.I-MAGES.CA. DNS.INITHOST.COM. CENTERSERVER.CWPNETWORK.CWP.ORG. MAIN.RONBYRNE.COM. NAIMONWEB1.NAIMONENTERPRISES.COM. NS1.KPLASTICS.COM. ROME.PUNIC.DEMONJO.COM. KITCHEN.PELIKANS.LOCAL. LAB.KPLAB.COM. NS.FORTECH.LV. NS1.MADKEY.COM. SERVER2000.HQ.NUANSABANDUNG.COM. MILO.MAXSONWORLD.COM. SERVER.EVERGREENVAIL.COM. CABER.BRUCE.SCOTSMEN.NET. ROOT1.RMI.NET. SM.NS1.SPACEMARINE.NET. MASTER-DOMAIN.COM. NS1.VRX.NET. CYTECH01.HQ.CYTECHNETWORKING.COM. WWW.COWS.SE. INTFELIX.FELIXSERVICE.COM. PEOPLE.WSTORE.NET. WEBNET.WEBDOM.LOCAL. TRANGO.GMG.GMG.COM. SEIT-WEB. ROCK.HQ.RCKTECH.COM. WIN2000-SERVER.HOME.LOCAL. SERVER01.ISU-UNI.COM. EI-DNS-PUB. HATHOR.EGYPT.SUPERDAN.COM. DS2.UHEALTHY.NET. DS1.UHEALTHY.NET. SERVER01.WORKGROUP.LOCAL. NS1.FINDMYMERCHANT.COM. WIN2000SVR-IIS1.IIS.SMARTVIEW.NET. MAIL.INTEGRATA.DE. DNS4.SABRINAAMS.COM. NS1.EASYPDF.COM. ICONSULTER.ICONSULTER.NET. RAMONA. RSMNT5.SOLUSII.COM. OWLKPWWW.NSP.WMDATA.COM. DDYNT.DDYWING.COM. INTERNET.TELE-CABLE.NET. HOME.THE-HIGHS.COM. NS.GELISIM.COM. INSWEB.INSEUROP.COM. WIN-SERVER. ENDOR.DARKTROOPERS.COM. BPSERVER. WEB2.WARDLAN.DUALPROC.NET. ANTIOCH.BEACOM.LOCAL. WPSDNS1. POST.IBCC.RU. ALPHA.BUILDCENTRAL.COM. NS1.RMPLLC.NET. WEB01.PRIMORDIAL.COM. DNS1.IISLINK.COM. HYBRID.PEARLMAGIK.COM. ESFAHAN.WORLDNETGROUP.NET. SUNE.TYRESO.SE. NS1.SURFSERVERS.COM. NS1.PROGENIC.COM. DNS1. WEBSERVER.CAMERONHUNT.COM. SF00.STAMPEDEFULFILLMENT.COM. SF10. TOR.NET-EZ0.COM. BIGBERTHA.KOCHENDORFER.COM. STUEY.STUBOT.NET. RUBY. IS01.DUD-ONLINE.DE. HYUNDAI-SERVER.HYUNDAI.LOCAL. 2K2.MAPCY.COM. WEBSERVER. 2KSERVER.DZTECH.LOCAL. INTERNETPENTIUM.LESSER-SOFTWARE.COM. WEBSVR.SPIRIT.FLYSPIRIT.COM. WWW0.WWW.RCSC. NS3.AFTERNIC.COM. EMC-DELTA.EUROSERVE.NET. EEK.HTTPD.COM. PA-SERVER.PHOTOAVENUE.PHOTOAVENUE.COM. CARTMAN.SF1.LDAPSOLUTIONS.NET. HOUDS15.METRONETWORKS.COM. DSRV1.SIMPLIFIED.NET. ABRAHAM.7817PPC.CHATLOSFAMILY.COM. SERVER01.DIGITAL-LANE.COM. MICRONETSERVER.MICRONET-USA.LOCAL. HOMEPROXY. WEBSERVER01.ANGUSWEB.ANGUS.ORG. CERVANTES.FUNBAGS.BOVER.NET. SPRINT2.ANARCHY.NA.EDU. NTSERVER.TOOHEY.TOOHEYCO.COM. ROBIN.FROG.GINTIS.COM. CEMA.DE. ZEUS.ONTINET.COM. TOMPLA.COM. METALLICA.ADVISORWORLD.COM. NS.ADVISIE.NL. HUMMER.CORP.SOSAVVY.COM. W.MAIL.NETABILITIES.COM. SUN.VBTECHTIPS.COM. DNS.PAPERLESSCORP.PAPERLESSCORP.COM. MSSV01.MICHIGANSOLUTIONS.COM. BRAIN.IMPEXPROD.IMPEX.COM. DAL5VAL2. MX.ALTERNIC.COM. KAESER-K7.KONSULTING.COM. KAESER_KONSULT.KONSULTING.COM. WEB1.COMPCONSULTING.NET. SMTP.PTSDOMAIN. PPISERVER2.PROPOINTWV.COM. ANNA.HERMOSAGURUS.HERMOSAGURUS.COM. DPC-GW. NS.WEBSERV.PCPROSOLUTIONS.COM. HOMER.BADILLOS.COM. DSRS5.DSRS.COM. NETSERVER.SEARA.PT. PL1600-1.HEXALOG.COM. SPOCK.NLP1. BONES2.NLPS.COM. NS.SPACE.NET. SF20175001.BLUE-ISR.FR. NS2.BRENT.NET. NS1.BRENT.NET. GW1.2BY2.LOCAL. 63.67.25.14 NS1.ALLPROSOUND.COM. MANDELA.REDSLASH.COM. MTL.MOMLALADENDARA.LOCAL. ZAPPA.BRENTEWOOD.COM. BIG450.MCPHARLIN.COM. MAIL2.DCSLREDBUS.LOCAL. WEB.DIABLOVALLEY.COM. IBN.IBNINFOSYS.COM. AQUANTA.EMAAL.COM. WIN2K.HOME.BRISTOWFAMILY.COM. NOC.MHSC.NET. MAIL1.BRADS.NET. WEB.BRADS.NET. TBWC. CSPC0006.PORRAHQ.PORRA.COM. A.OPEN-NIC.ORG. DNS01. SHELL.GCIS.NET. NS.SHOPPING-ELECTORNICS.COM. MAIL.PROMATCH.NET. NS2.KEYFILES.NET. NS1.KEYFILES.NET. SCRNET.COM. AD.POLLYCHRONE.COM. SVAD01.LIVINGNEXUS.COM. MICROVEX1.NS1.MICROVEX.NET. SERVER1.KWREALITY.COM. BOSSY.IDENNY.COM. NS1.COUNCIL.NET. NS2.COUNCIL.NET. AWSWEB.AWS.AUTOSITEEXPRESS.COM. SERVER01.ISRAEL.KONNEKTUS.COM.
[IFWP] New TLD Proposed dot.here
Title : Top Level DNS Name for addressing by physical context Author(s) : L. Yeoh Filename: draft-yeoh-tldhere-00.txt Pages : 2 Date: 03-Nov-00 This document proposes the reservation of a special use TLD ( .here. ) to allow a more convenient addressing of devices by general physical location or context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-yeoh-tldhere-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-yeoh-tldhere-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: [EMAIL PROTECTED] In the body type: "FILE /internet-drafts/draft-yeoh-tldhere-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <[EMAIL PROTECTED]> ENCODING mime FILE /internet-drafts/draft-yeoh-tldhere-00.txt <ftp://ftp.ietf.org/internet-drafts/draft-yeoh-tldhere-00.txt> --- end forwarded text Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Re: Roots servers on rise - ICANN's golden egg cracking
On Sun, 5 Nov 2000 [EMAIL PROTECTED] wrote: > #Last year alternate roots supported 0.3% of internet traffic. > # > #This year alternate roots are supporting 5.5% of internet traffic. > # > #The BIND study this year to date has ennumerated 60,513 dns (15% of > #399,937 dns) of which 3,331 report they are using non-USG roots. > > Don't "alternate roots" have to have a copy of > what the main root servers have? Then they are > doing a favor by off-loading traffic. Not all the time. I've noticed some corporations (big ones like hyundai) use their own roots to block traffic to their employees. There's a wildcard record in the root so that if an employee goes to www.sex.com they end up at www.hyunai.com - or something to that effect. > Separately, I've noticed something on my Solaris 8 box. > > I often freeze my Netscape browser windows when leaving > the computer for a while. That's because FoxNews and NYT > (for example) keep reloading themselves again and again. > This is unwanted push traffic. It's not costing me anything > over my DSL/Cable modems, it's just unwanted by me. > > Even with browsers frozen... > > I recently left 'snoop' running, and found I was initiating > DNS traffic...to FoxNews and NYT. Looking closer, I had DNS > queries regarding non-browser-accessed sites, like ftp. That is odd. DNS can carry alot more then just dns. Maybe that's whats' hapeening. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] The Internet Namespace Cooperative Root Sync Report Mon Nov 6 05:34:51 EST 2000
The Internet Namespace Cooperative Root Sync report for Mon Nov 6 05:34:51 EST 2000 http://www.tinc-org.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE >>> delete ns NS.DNS.BE. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root LA - ERROR detected in zone .LA <<< add ns A.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns E.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root >>> delete ns AUTH03.NS.UU.NET. from root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root >>> delete ns DNSSEC2.SINGNET.COM.SG. from root >>> delete ns DNSSEC3.SINGNET.COM.SG. from root >>> delete ns NS.RIPE.NET. from root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root
[IFWP] Open Root Server Confederation Root Sync Report Mon Nov 6 05:31:38 EST 2000
Open Root Server Confederation Root Sync report for Mon Nov 6 05:31:38 EST 2000 http://www.open-rsc.org/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE >>> delete ns NS.DNS.BE. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root
[IFWP] i-DNS.net International Root Sync Report Mon Nov 6 05:30:00 EST 2000
i-DNS.net International Root Sync report for Mon Nov 6 05:30:00 EST 2000 http://www.i-DNS.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ BE - ERROR detected in zone .BE >>> delete ns NS.DNS.BE. from root DK - ERROR detected in zone .DK <<< add ns NS4.TELE.DK. to root EC - ERROR detected in zone .EC <<< add ns A.I-DNS.NET. to root <<< add ns B.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns D.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root LA - ERROR detected in zone .LA >>> delete ns B.I-DNS.NET. from root >>> delete ns D.I-DNS.NET. from root MT - ERROR detected in zone .MT >>> delete ns SPARKY.ARL.MIL. from root SE - ERROR detected in zone .SE >>> delete ns SPARKY.ARL.MIL. from root
[IFWP] Re: Re[4]: Roots servers on rise - ICANN's golden egg cracking
On Sun, 5 Nov 2000, William X. Walsh wrote: > > I understand. In fact the estimate is correct. Unfortuantely I don't > > have the time to teach you statistical analysis. But we can be confident > > that 5% of internet traffic is non USG. My results are representative and > > can be extrapolated accordingly with some confidence. > > You have absolutely no basis for making that assumption. The number > of nameservers queried is in no way directly representative of the > number of nameservers actually used for end user name resolution, nor > of the number of queries made on a per server basis. No it in fact does. There are some 300,000 dns in the dot.com file, to date 60,513 have been surveyed (15%). It's easy and completely acceptable to extrapolate from there. And furthermore the existing population enumerated is more then enough to extrapolate from. > > To make the claim you made, you would need a lot more data than you > can get from doing the simple queries you are doing, and as a matter > of fact this would require the co-operation of the nameserver > operators. > > Your method is not scientific, and it no statistician would ever make > the leap in logic you tried to make here. Get yourself a statistician and I'll be happy to provide him with the numbers. Like I always say - talk is cheap and evidence dont lie '=) regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: Re[2]: Roots servers on rise - ICANN's golden egg cracking
On Sun, 5 Nov 2000, William X. Walsh wrote: > That is not what you said in the original post, this is: > > >> >>Last year alternate roots supported 0.3% of internet traffic. > >> >> > >> >>This year alternate roots are supporting 5.5% of internet traffic. > > You have no basis for saying how much traffic the servers that may not > be using the USG roots are supporting out of the whole internet > traffic in the method you used to survey them. The percentage of > nameservers does not automatically equate to the percentage of > internet traffic. I understand. In fact the estimate is correct. Unfortuantely I don't have the time to teach you statistical analysis. But we can be confident that 5% of internet traffic is non USG. My results are representative and can be extrapolated accordingly with some confidence. I know this is a shock to you william. But thats' life and it don't surprise me. > > The bottom line here is that my predictions that ICANN would lose market > > share are right on. Last year it was at 99.7% and this year it's at > > 94.5%. > > Again, your statement doesn't jive with the actual results of your > "survey". > > In other words, Joe, you are trying to make this number appear to be > more substantive than it is. But I understand why perfectly :) > > But let's make sure we stick to the actual facts in evidence, ok? The facts are very simple. Of 60,513 dns surveyed, 3,331 reported as non USG. This is a big change from last year. Those are the facts and I can support them. In fact what I have is more then "facts" - it is evidence and proof. Like I said - anyone willing to undertake to test and confirm my results is welcomed. Because evidence like this William can be tested and verified. All your doing is jive turkey talk. If you want to challenge my stats William - accept the undertaking and test them for yourself. We call that process William - the scientific method. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: Roots servers on rise - ICANN's golden egg cracking
On Sun, 5 Nov 2000, William X. Walsh wrote: > Hello Ron, > > Sunday, November 05, 2000, 5:28:03 PM, you wrote: > > > At 06:34 PM 11/5/00 -0500, !Dr. Joe Baptista wrote: > >>Last year alternate roots supported 0.3% of internet traffic. > >> > >>This year alternate roots are supporting 5.5% of internet traffic. > > > I wonder how long this will be permitted to continue before > > ICANN, DoC, WIPO, etc *require* everyone to use USG roots...? > > His statistic is bogus. He has absolutely no real basis for saying how > much of the internet traffic is using the alternative roots in this > way. Anyone interested in verifying my results is welcomed to do so. The claim is as follows, of the 60,513 dns surveyed 3,331 reported using non-USG roots. A sample of this size has a standard error of +/- 1.6509% with a 95% confidence. So I'm very confident were seeing a trend away from ICANN. William if your willing to provide me with an undertaking that you will verify my data then i'll send you the ip's already tested and you'll see the results are correct. If not - shut your uneducated pie hole. The bottom line here is that my predictions that ICANN would lose market share are right on. Last year it was at 99.7% and this year it's at 94.5%. Regards Joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] Roots servers on rise - ICANN's golden egg cracking
Last year alternate roots supported 0.3% of internet traffic. This year alternate roots are supporting 5.5% of internet traffic. The BIND study this year to date has ennumerated 60,513 dns (15% of 399,937 dns) of which 3,331 report they are using non-USG roots. In my opinion - this is significant. And it puts a whole new twist on the song - what a difference a day makes. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Regland
Touton really comes off as a hitler type. According to regland he does
alot of screaming during the course of business - i wonder if he bites
rugs too? strange boy.
If you have any questions, Please contact Regland, Inc. at
210-495-9800
CAUSE NO. __
REGLAND, INC. § IN
THE DISTRICT COURT
§
Plaintiff, §
§
VS.
§
§ OF BEXAR COUNTY, TEXAS
INTERNET CORPORATION FOR§
ASSIGNED NAMES AND NUMBERS §
A/K/A ICANN AND LOUIS TOUTON, §
INDIVIDUALLY, §
§
Defendants.
§ __ JUDICIAL DISTRICT
PLAINTIFF'S ORIGINAL PETITION
TO THE HONORABLE JUDGE OF SAID COURT:
COMES NOW REGLAND, INC., Plaintiff in the above-numbered and styled
cause, complaining of the Internet Corporation for Assigned Names and
Numbers a/k/a ICANN and Louis Touton, individually, and for cause of
action respectfully would show the following:
I.
DISCOVERY CONTROL PLAN
1.1 Plaintiff designates this case, under Texas Rule of Civil
Procedure 190.3, to be governed by a Level 2 Discovery Control Plan.
II.
PARTIES AND SERVICE
2.1 Plaintiff RegLand, Inc. ("RegLand" or "Plaintiff") is a
corporation organized under the laws of the State of Texas.
2.2 Defendant Internet Corporation for Assigned Names and
Numbers a/k/a ICANN ("ICANN") is a nonprofit corporation organized
under the California Nonprofit Public Benefit Corporation Law, which
may be served with process by delivering a copy of the citation
together with this Plaintiff's Original Petition, upon its registered
agent, CT Corporation System, 818 West Seventh St., Los Angeles, CA.
90017.
2.3 Defendant Louis Touton ("Touton") is an individual resident
of the State of California, who may be served with process by
delivering a copy of the citation together with this Plaintiff's
Original Petition, upon him at his place of business located at 4676
Admiralty Way #330, Marina Del Rey CA. 90292, or wherever he may be
found.
III.
VENUE AND JURISDICTION
3.1 Venue is proper in Bexar County, Texas, because Bexar County
is where all or a substantial part of the events or omissions giving
rise to the claim occurred and/or plaintiff resided in Bexar County,
Texas, at the time of the accrual of the cause of action.
3.2 Jurisdiction is proper in this Court because the amount in
controversy is within the jurisdictional limits of this Court.
IV.
FACTUAL BACKGROUND
4.1 ICANN is a technical coordination body for the Internet.
ICANN was created in October 1998 by a coalition of the Internet's
business, technical, academic, and user communities. The purpose
behind the creation of ICANN was for it to assume responsibility for a
set of functions previously performed under U.S. government contract
by IANA and other groups. Specifically, ICANN is to coordinate the
assignment of the following identifiers that must be globally unique
for the Internet to function: Internet domain names; IP address
numbers; protocol parameter and port numbers. In addition, ICANN is
supposed to coordinate the stable operation of the Internet's root
server system. ICANN has no other authority or purpose. ICANN's
Memorandum of Understanding with the U.S. Department of Commerce
specifically states that it shall not act unjustifiably or arbitrarily
to injure particular persons or entities or particular categories of
persons or entities.
4.2 When founded, ICANN was purportedly dedicated to preserving
the operational stability of the Internet; to promoting competition;
to achieving broad representation of global Internet communities; and
to developing policy through private-sector, bottom-up,
consensus-based means. Regrettably, ICANN has become an instrument by
which a few individuals attempt to impose their will upon the very
communities they were supposed to serve. One of those individuals is
Touton.
4.3 Touton is Vice-President, Secretary, and General Counsel of
ICANN. Although neither ICANN's Articles of Incorporation or its
By-Laws impute any policy-making authority upon Touton, due to his
position, he wields considerable power and influence over the Internet
community. Touton is subjectively aware of this power and influence,
which he uses to the detriment of those who defy him or his own view
of what the Internet is or should be.
[IFWP] In the event of an emergency - PULL HERE
I expect this year there will be a massive attack against the USG roots. To date the USG roots have been exposed to numerous attacks. Recently I understand that icmp to the servers was turned off to ward off a DDOS. I'm increasingly concerned that one of these days someone is going to be successfull and this mucked up system is going to go offline for awhile. But were ready for that. I've just launched DEBS (Domain Emergency Broadcast System). In the event of an emergency i'll have the capability to push the button and save the world. I hate instability and DEBS helps me sleep better at night. DEBS is an emergency email system which is independent of the DNS and maps dns email addresses directly to MX. In the event of a USG brown out (which I expect soon) you can be assured that DEBS will reach out and touch alot of people. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] new root servers
I'll tell ya - I've never seen so many roots in my bind database. The attached list is the most recent lists based on an enumeration of only 10% of listed dns. There are significant changes occuring in the dns infrastructure, and I think we owe that all to icann. A really interesting note is that a new root service "REALNAME" seems to be taking off big time in the orient (korea mainly). A.ROOT-SERVERS.ORSC. A.ROOT-SERVERS.NET. NS.INTERLIANT.COM. NS1.FUTUREQUEST.NET. TINC-ORG.COM. REALNAME. SYS01.INAME.NET. NS1.DOMAINS.COM. RS2.AURSC.AH.NET. HOME.KASHPUREFF.ORG. EUGENE.KASHPUREFF.ORG. A.I-DNS.NET. KVINSLAND.SKPTE.ORG. KAPPA.CROWNINTL.COM. NS1.WWW.HOUDAT.NET. SERVER.TEAMBYRON.COM. BANSHEE.MYBIS.COM. 3TY.BROADI.COM. NS1.WERCS.COM. NS1.ROOT.OPENNIC. WWW.EDUSYSTEM.CO.KR. YANC001FS.YPC.COM. ADMINW2K.NS1.MROUTLAW.COM. ADS.DPIDVAR.COM. NS1.DNSUSA.ORG. RIONEGRO.RIONEGRO.CUBOSOFT.NET. ALEXA.IOGLYPHIX.NET. MEGABYTE.ALIVENEWMEDIA.MB.CA. ARGUS.AMHERST.KILLERWEBSITE.COM. SERVER3.TCCF.NET. DATARAD.DATARAD.INTRA. PROCSY.PROCSYS.KWANGWOON.AC.KR. SCIRONSRV.SCIRON.SCIRON.SE. KEG-DEPOT.DDA.DDAONLINE.COM. NS.CNSOFT.DE. CNA-GDWI-0.CNA.AT. NCR.ND.EDU. DOMAINSRVR.GRINNELL.EDU. BMERH365.CA.NORTEL.COM. EENETSVR.EENET.COM.TW. BLACKBOX.75CONCORD.75CONCORD.COM. CEREBUS.NEW-SCOTLAND.COM. MCIS01. UA1.REDDEERNET.COM. JTAIME.NET. NT2000. SERVER.DONE-THAT.COM. IWHSERVER.IWH.COM. COLONEL-HATHI.KO-NP.DE. JULIET.EBIZS.NET. ROMEO.EBIZS.NET. JASMINE.RPPIA.COM. NT.W2K.POLEIS.NET. ALPHA.WAYGEE.COM. DMAXNTPDC01.DMAXUSFLTAM. NET1.HOME.WIN2KTECH.COM. WWW.WALDENS.COM. MERLIN.I-MAGES.CA. DNS.INITHOST.COM. CENTERSERVER.CWPNETWORK.CWP.ORG. MAIN.RONBYRNE.COM. NAIMONWEB1.NAIMONENTERPRISES.COM. NS1.KPLASTICS.COM. ROME.PUNIC.DEMONJO.COM. KITCHEN.PELIKANS.LOCAL. LAB.KPLAB.COM. NS.FORTECH.LV. NS1.MADKEY.COM.
[IFWP] Re: Ken Stubbs @ core deletes vote-auction.com
our ol friend Ken is up to no good again. On Fri, 3 Nov 2000, Tom Vogt wrote: > > it seems that core (i.e. the root servers) has deleted the entry for > vote-auction.com - while the whois still works and their primary > nameserver (in austria) still resolves, a regular lookup returns with > "host unknown". > > rumour has it that core carved in to demand by most possibly the feds. > here in europe the sentiment today is that by doing so core has stopped > being (if it ever was) an independent and purely technical instance and > has entered the realm of politics. for example, no matter whether or not > vote-auction.com is or is not illegal in the US, what business has a US > court or lea in blocking the site for *me* (in germany) or, for that > matter, the rest of the planet? > -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] BIND Versions Reported (fwd)
One of the joys of running the BIND surveys is reading all the reported version of BIND running on various servers. From time to time you get some admins who block the bind report and replace it with one of their own ditties. And I think that's fun. If you scan this list you'll find some of the personal replys many admins include in the chaos version reply. One interesting trend is that their are more replies like this, which suggest to me people are hiding their bind version for reasons of security. As you all know Paul Vixies bind has been broken since day one, so this really is not an efficient method - it only slows down the potential hackers who has to try various different bind vulnerabilities before they have success. But it slows them down and that's important. regards joe -- Forwarded message -- Date: Thu, 2 Nov 2000 09:49:46 -0500 To: [EMAIL PROTECTED] Subject: BIND Version Reports $Id: dns,v 3.20 2000/06/20 14:19:45 gdmr Exp $ %VERSION% 'Tis enough (BIND 4.9.5-p1) 0 0.1 1 1.0 1.1.0 10 10.03.22P18 2xs nameserver v0.43 3.1.3.STABLE37 4.2.0 4.2.1 4.9.3-P1-plus-CA-98.05-patches 4.9.3-beta9-patch1 4.9.5 4.9.6 4.9.6 #0: 4.9.6-REL 4.9.6-REL-Interceptor 4.9.7 4.9.7-REL 4.9.7-REL 990303.111407 4.9.7-REL 990730.160207 4.9.7-T1B 5.7 509CS-SCBBK 6.6.6 8.1-REL 8.1.1 8.1.2 8.1.2+RandomID+SpoofWarn 8.1.2-REL 8.1.2-SGI_fw 8.1.2-SU 8.1.2-T3B 8.1.2.666 8.2 8.2-REL 000208.162217 8.2.1 8.2.1-T4B 8.2.1-T6B 8.2.2-P3 8.2.2-P3+patch4 8.2.2-P3p4 8.2.2-P4 8.2.2-P5 8.2.2-P5-IDNS 8.2.2-P5-LB-0.3 8.2.2-P5-NOESW 8.2.2-P5-SU 8.2.2-P6 8.2.2-REL 8.2.2-T3B 8.2.2-T7B 8.2.2-T8B 8.2.2P5 8.2.3-T1A 8.2.3-T2B 8.2.3-T3B 8.2.3-T4B 8.2.3-T5B 8.2.3-T6B 8.2.3-T7B 8.8.2 P5 8.something 9.0.0 9.0.0rc1 9.0.0rc3 9.0.0rc4 9.0.0rc6 970930.9/18/97M38 980805.3/26/98M30 990413.3/26/98M58 991001.3/26/98M22 991007.3/26/98M24 :-) ??? ? ?.? A version of BIND 8 ALL_QUERIES_LOGGED AOL Web DNS Answer hazy. Ask again later. As if I would give you my version... As if I'd tell you ... BIND BIND 8.1.2 BIND 8.2.2 BIND 8.2.2 patchlevel5 BIND 8.2.2-P5 BIND dns.schna.org CTSNET Nameserver Contact '[EMAIL PROTECTED]' for this information Contact [EMAIL PROTECTED] Curiosity.Killed.The.Cat Curious, eh? ;-))) DNS DNS Fluxus DNS Pro version 5.7 by FBL Inc. DeEnesse Denied Disabled due to security Disabled for security Disabled, if you have a legitimate reason. email [EMAIL PROTECTED] Error 3186-X: Contact your systems administrator. Exactis-x.x.x Explain to [EMAIL PROTECTED] why you need to know. FHS Test DNS Server FUNET BIND GMD-Darmstadt bind8 Go away Go away, loser! Go away. HOHO!! JUST MAKE YOUR MIND FLY Hallo, ich bin der neue:-) Have a nice day! Hello Huh? I don't think so I have an a-version to answering INS-6.6.6 Ich verstehe nicht If you have a legitimate reason for requesting this information, please contact <[EMAIL PROTECTED]> If you really need to know, e-mail [EMAIL PROTECTED] If you really want to know email [EMAIL PROTECTED] Incognito DNS Commander 1.5.0.10 (built Aug 4 1998) [up=9d36068s] Incognito DNS Commander 6.00.60 (built Jun 10 1999) [up=0d10911s] Incognito DNS Commander 6.00.60 (built Jun 10 1999) [up=0d9893s] Info Avenue Forever 1.0 Jakis tam BIND chyba :) Just send your damn query already Keep your hands off here! Kyaritsu DNS-Cache v0.91 LOCAL-000111.193104 LOCAL-000327.202928 LOCAL-000808.132048 LOCAL-980501.020913 LOCAL-980513.015103 LOCAL-980607.103805 LOCAL-980621.134102 LOCAL-980812.085705 LOCAL-980917.042027 LOCAL-990114.122553 LOCAL-990324.212218 LOCAL-990504.210254 LOCAL-990615.223055 LOCAL-990616.142144 LOCAL-990617.161341 LOCAL-990812.185318 LOCAL-990907.152943 LOCAL-990909.093038 LOCAL-991203.211721 LinuxSuckz Meow! Meow! Meta IP/DNS V4.0 - BIND V8.1.2 (Build 4411 ) Meta IP/DNS V4.0 - BIND V8.1.2 (Build 4426 ) Meta IP/DNS V4.0 - BIND V8.1.2 (Build 4435 ) Meta IP/DNS V4.1 - BIND V8.1.2 (Build 4657 ) Meta IP/DNS V4.1 - BIND V8.1.2 (Build 4679 ) Meta IP/DNS V4.1 - BIND V8.1.2 (Build 4704 ) Meta IP/DNS V4.1 - BIND V8.2.2-P6 (Build 4855) Meta IP/DNS V4.1 - BIND V8.2.2-P6 (Build 4883) Meta IP/DNS V4.1, Build 4704 BIND V8.1.2 Microsoft Engineers are Weenies MyBind 1.0 N.O.Y.B N/A NO!!! Name's BIND...James BIND... New enough Nick off! 8.1.2 Non, ca va non ? None of your business None of your damn business. None_of_your_business Nortel Networks - What do you want the Internet to be? Nosy, nosy! Not Available Not authorized Not telling Not today, and not tomorrow either. OBSD-8.2.2-P5 Oh, go smurf yer mama! PROPRIETARY-nsa PROPRIETARY-nsb PSINet Paprika Permission denied. Petras DNS Philips Research Labs, NY - 8.2.2-P5 QDDNS 2.0 QDDNS 2.1 QDDNS 3.0 QMS Ranger Seaweed3.7 Secured See Mars Segmentation error. Sektornet Smile for the camera... Sorry, bitch. Maybe next time... Surely you must be joking Surely you must be joking... Surely you must be kidding. Surely, you must be joking. Take a guess.. That information is not available Try mail for that. Unauthorised Access Prohibited Uncle Bud's DNS, Coon-dog revision
[IFWP] alternative roots on the rise
The bind 2000 survey will be finished in about three weeks. This bind survey also collects data on the usage of alternate roots. I conducted a survey of roots a few months ago and based on a review of the raw data I can say with some confidence that there are more root servers today with the bulk showing up in the orient. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] More from ester - Esther's reply on spamming (fwd)
-- Forwarded message -- Date: Mon, 30 Oct 2000 08:33:39 -0800 From: Bill Stewart <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Esther's reply on spamming >To: Bill Stewart <[EMAIL PROTECTED]> >From: [EMAIL PROTECTED] (Esther Dyson) >Subject: Re: Were you really spamming people? I'm surprised. >Date: Mon, 30 Oct 2000 07:14:13 -0500 > >You might as well. It won't fix anything, I'm sure, but at least I had the >courage to respond. And what I say below is the truth; we still do talk >about this internally and I'm not sure what's the ideal approach. (A number >of people *do* say what you said: It's interesting to know what I'm up to. >I respond to everyone who responds to the mailing other than bounces.) So, >yes, I'd be happy to engage in argument (as opposed to flaming). > >Esther > >At 10:42 AM 10/29/00 -0800, Bill Stewart wrote: >>Esther - thanks. Actually, no need to remove me; while I'm not >>going to subscribe to Release 1.0, it's still interesting to know >>what you're doing. Is it ok if I forward your mail on to Cypherpunks, >>or alternatively to Tim? >> >> Thanks; Bill >> >>At 08:37 AM 10/29/00 -0500, Esther wrote: >>>Your definition may vary, but yes, we sent out a mailing to people who one >>>way or another have given me cards, corresponded with me, etc. I don't >>>honestly know how Tim got onto our list, but we'll take him off right away. >>> >>>In fact, as you can see below, we invite people to ask to be removed, and if >>>they do, we remove them immediately. (It's nicer when they ask us >>>directly, but we'll treat this as a removal request from both you and Tim!) >>> >>>And yes, this troubles me a little, but overall I am more concerned about >>>the use of confidential data to invade someone's privacy, than about the >>>issue of spam. (I get enough of it, especially over ICANN, to know that >>>it's annoying.but harmless.) I'm on record that people should (and will) >>>be able to filter their own spam, but that they do need to be able to rely >>>on promises of confidentiality when they deal with others. That's a somewhat >>>different issue. >>> >>>Esther >>> >>>At 01:21 AM 10/29/00 -0700, Bill Stewart wrote: Hi, Esther - this message got sent to the Cypherpunks list, and several other people pointed to references about you sending out advertising email to people other than your conference attendees or people who'd requested more information. I'm really surprised - it doesn't sound like something you'd do. Also, I tried to check out the release1-0.com web site, and it said something about the RPC server being too busy. Thanks; Bill Stewart ... [Tim's message, deleted] >>> >>>HIGH-TECH-FORUM, BARCELONA, NOVEMBER 1 TO 3 >>>http://www.edventure.com/htforum2000.html >>> >>>Esther Dyson Always make new mistakes! >>>chairman, EDventure Holdings >>>chairman, Internet Corp. for Assigned Names & Numbers >>>[EMAIL PROTECTED] >>>1 (212) 924-8800-- 1 (212) 924-0240 fax >>>104 Fifth Avenue (between 15th and 16th Streets; 20th floor) >>>New York, NY 10011 USA >>>http://www.edventure.comhttp://www.icann.org >>> >>>PC Forum: 25 to 28 March 2001, Scottsdale (Phoenix), Arizona Thanks! Bill Bill Stewart, [EMAIL PROTECTED] PGP Fingerprint D454 E202 CBC8 40BF 3C85 B884 0ABE 4639
[IFWP] RE: Fw: i-DNS.net International Root Sync Report Sat Oct 28 22:24:10 EDT 2000
good idea - i'll incorporate it into the facility next month. regards joe On Mon, 30 Oct 2000, Roeland M.J. Meyer wrote: > Hey Joe, > > You could try consolidating the reports into a single e-mail, like Tony > Bates does with the CIDR report (call it the ROOT report) and include NANOG. > > > > -Original Message- > > From: Joe Baptista [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, October 29, 2000 6:12 PM > > To: James Seng > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; NCDNHC > > Subject: Re: Fw: i-DNS.net International Root Sync Report Sat Oct 28 > > 22:24:10 EDT 2000 > > > > > > > > This is a public distribution and I'm not complaining. From now on > > everyone get's checked and everone has an opportunity to fix > > themselves. > > > > I'm sick and tired of root server operations outside the > > legacy being run > > like some candy consession. If ya can't stand the heat baby > > get out of > > the kitcken. Frankly I'm sick and tired of badly run root zones > > embarrasing me. So enough with the crocadile tears and get it fixed. > > > > Reports will be automatically published weekly each monday > > night. If you > > want to take advantage of it their published to domain > > policy, some comp > > news group on domains, and alt.fan.joe-baptista (need i say more). > > > > regards > > joe > > > > On Mon, 30 Oct 2000, James Seng wrote: > > > > > Hi Joe, > > > > > > You know, posting this to a list where no i-DNS.net staff > > is lurking around is > > > actually quite pointless because we would not know your > > complains. You should > > > have easily cc: [EMAIL PROTECTED] ;-) > > > > > > Anyhow, I got my technical operations looking into this now. > > > > > > -James Seng > > > > > > > - Original Message - > > > > From: Joe Baptista <[EMAIL PROTECTED]> > > > > To: NCDNHC <[EMAIL PROTECTED]> > > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > > Sent: Sunday, October 29, 2000 10:37 AM > > > > Subject: Re: i-DNS.net International Root Sync Report Sat > > Oct 28 22:24:10 > > > > EDT 2000 > > > > > > > > > > > > > > > > > > Our friends at i-dns should really fix their roots - soon. > > > > > > > > > > On Sat, 28 Oct 2000, Joe Baptista wrote: > > > > > > > > > > > > > > > > > i-DNS.net International Root Sync report: Sat Oct 28 > > 22:24:10 EDT 2000 > > > > > > http://www.i-DNS.net/ > > > > > > > > > > > > AL - ERROR detected in zone .AL > > > > > > <<< ERROR root missing ns ITGBOX.IAT.CNR.IT. > > > > > > >>> ERROR delete ns ITGBOX.CNUCE.CNR.IT. from root > > > > > > > > > > > > AN - ERROR detected in zone .AN > > > > > > <<< ERROR root missing ns ENGINE1.UNA.NET. > > > > > > > > > > > > AT - ERROR detected in zone .AT > > > > > > <<< ERROR root missing ns NS3.AUSTRIA.EU.NET. > > > > > > <<< ERROR root missing ns NS7.UNIVIE.AC.AT. > > > > > > >>> ERROR delete ns ALIJKU01.EDVZ.UNI-LINZ.AC.AT. from root > > > > > > >>> ERROR delete ns NS.AUSTRIA.EU.NET. from root > > > > > > > > > > > > BE - ERROR detected in zone .BE > > > > > > <<< ERROR root missing ns MASTER.DNS.BE. > > > > > > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > > > > > > > > > > > BO - ERROR detected in zone .BO > > > > > > <<< ERROR root missing ns AUTH100.NS.UU.NET. > > > > > > >>> ERROR delete ns WARA.BOLNET.BO. from root > > > > > > > > > > > > BY - ERROR detected in zone .BY > > > > > > <<< ERROR root missing ns NS2.SCSI.GOV.BY. > > > > > > <<< ERROR root missing ns SUN.SCSI.GOV.BY. > > > > > > > > > > > > CA - ERROR detected in zone .CA > > > > > > <<< ERROR root missing ns MERLE.CIRA.CA. > > > > > > <<< ERROR root missing ns RS0.NETSOL.COM. > > > > > > >>> ERROR delete ns RS0.INTERNIC.NET.
[IFWP] Re: Namespace and i-DNS.net International Root Sync Report Mon Oct30 05:30:01 EST 2000
Good news - i-dns is almost fixed. Now all they have to do is recognize themselves for their own cctlds and their fixed. To be frank cctld .LA was only established this past week - so everyone was caught on that one. On Mon, 30 Oct 2000, Joe Baptista wrote: > i-DNS.net International > Root Sync report for Mon Oct 30 05:30:01 EST 2000 > http://www.i-DNS.net/ > > (c) The dot.GOD Registry @ http://www.dot-god.com/ > > EC - ERROR detected in zone .EC > <<< add ns A.I-DNS.NET. to root > <<< add ns B.I-DNS.NET. to root > <<< add ns C.I-DNS.NET. to root > <<< add ns D.I-DNS.NET. to root > <<< add ns ECNET.EC. to root > <<< add ns ECUA.NET.EC. to root > <<< add ns F.I-DNS.NET. to root > >>> delete ns NS1.I-EMAIL.NET. from root > >>> delete ns NS2.I-EMAIL.NET. from root > > LA - ERROR detected in zone .LA > <<< add ns A.I-DNS.NET. to root > <<< add ns C.I-DNS.NET. to root > <<< add ns E.I-DNS.NET. to root > <<< add ns F.I-DNS.NET. to root > >>> delete ns NS1.I-EMAIL.NET. from root > >>> delete ns NS2.I-EMAIL.NET. from root > on another positive note - namespace has fixed all it's problems. There are no errors no longer in their root. Unfortunately their still forging the SOA header and pretending their the nsiregistry. In fact namespace did chenge their SOA from the old internic forgery to the new nsiregistry forgery. I wonder why they do that - most illogical. But at least they now have a clean root, even if it advertises itself as a forgery - at least it's a forgery that works. . 1D IN SOA A.ROOT-SERVERS.NET. hostmaster.nsiregistry.NET. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] The Internet Namespace Cooperative Root Sync Report Mon Oct 30 05:34:27 EST 2000
The Internet Namespace Cooperative Root Sync report for Mon Oct 30 05:34:27 EST 2000 http://www.tinc-org.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ LA - ERROR detected in zone .LA <<< add ns A.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns E.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root >>> delete ns AUTH03.NS.UU.NET. from root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root >>> delete ns DNSSEC2.SINGNET.COM.SG. from root >>> delete ns DNSSEC3.SINGNET.COM.SG. from root >>> delete ns NS.RIPE.NET. from root
[IFWP] Open Root Server Confederation Root Sync Report Mon Oct 30 05:31:39 EST 2000
Open Root Server Confederation Root Sync report for Mon Oct 30 05:31:39 EST 2000 http://www.open-rsc.org/ (c) The dot.GOD Registry @ http://www.dot-god.com/ LA - ERROR detected in zone .LA <<< add ns A.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns E.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root >>> delete ns AUTH03.NS.UU.NET. from root >>> delete ns DNSSEC1.SINGNET.COM.SG. from root >>> delete ns DNSSEC2.SINGNET.COM.SG. from root >>> delete ns DNSSEC3.SINGNET.COM.SG. from root >>> delete ns NS.RIPE.NET. from root
[IFWP] i-DNS.net International Root Sync Report Mon Oct 30 05:30:01 EST 2000
i-DNS.net International Root Sync report for Mon Oct 30 05:30:01 EST 2000 http://www.i-DNS.net/ (c) The dot.GOD Registry @ http://www.dot-god.com/ EC - ERROR detected in zone .EC <<< add ns A.I-DNS.NET. to root <<< add ns B.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns D.I-DNS.NET. to root <<< add ns ECNET.EC. to root <<< add ns ECUA.NET.EC. to root <<< add ns F.I-DNS.NET. to root >>> delete ns NS1.I-EMAIL.NET. from root >>> delete ns NS2.I-EMAIL.NET. from root LA - ERROR detected in zone .LA <<< add ns A.I-DNS.NET. to root <<< add ns C.I-DNS.NET. to root <<< add ns E.I-DNS.NET. to root <<< add ns F.I-DNS.NET. to root >>> delete ns NS1.I-EMAIL.NET. from root >>> delete ns NS2.I-EMAIL.NET. from root
[IFWP] Re: Fw: i-DNS.net International Root Sync Report Sat Oct 28 22:24:10EDT 2000
This is a public distribution and I'm not complaining. From now on everyone get's checked and everone has an opportunity to fix themselves. I'm sick and tired of root server operations outside the legacy being run like some candy consession. If ya can't stand the heat baby get out of the kitcken. Frankly I'm sick and tired of badly run root zones embarrasing me. So enough with the crocadile tears and get it fixed. Reports will be automatically published weekly each monday night. If you want to take advantage of it their published to domain policy, some comp news group on domains, and alt.fan.joe-baptista (need i say more). regards joe On Mon, 30 Oct 2000, James Seng wrote: > Hi Joe, > > You know, posting this to a list where no i-DNS.net staff is lurking around is > actually quite pointless because we would not know your complains. You should > have easily cc: [EMAIL PROTECTED] ;-) > > Anyhow, I got my technical operations looking into this now. > > -James Seng > > > - Original Message - > > From: Joe Baptista <[EMAIL PROTECTED]> > > To: NCDNHC <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Sunday, October 29, 2000 10:37 AM > > Subject: Re: i-DNS.net International Root Sync Report Sat Oct 28 22:24:10 > > EDT 2000 > > > > > > > > > > Our friends at i-dns should really fix their roots - soon. > > > > > > On Sat, 28 Oct 2000, Joe Baptista wrote: > > > > > > > > > > > i-DNS.net International Root Sync report: Sat Oct 28 22:24:10 EDT 2000 > > > > http://www.i-DNS.net/ > > > > > > > > AL - ERROR detected in zone .AL > > > > <<< ERROR root missing ns ITGBOX.IAT.CNR.IT. > > > > >>> ERROR delete ns ITGBOX.CNUCE.CNR.IT. from root > > > > > > > > AN - ERROR detected in zone .AN > > > > <<< ERROR root missing ns ENGINE1.UNA.NET. > > > > > > > > AT - ERROR detected in zone .AT > > > > <<< ERROR root missing ns NS3.AUSTRIA.EU.NET. > > > > <<< ERROR root missing ns NS7.UNIVIE.AC.AT. > > > > >>> ERROR delete ns ALIJKU01.EDVZ.UNI-LINZ.AC.AT. from root > > > > >>> ERROR delete ns NS.AUSTRIA.EU.NET. from root > > > > > > > > BE - ERROR detected in zone .BE > > > > <<< ERROR root missing ns MASTER.DNS.BE. > > > > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > > > > > > > BO - ERROR detected in zone .BO > > > > <<< ERROR root missing ns AUTH100.NS.UU.NET. > > > > >>> ERROR delete ns WARA.BOLNET.BO. from root > > > > > > > > BY - ERROR detected in zone .BY > > > > <<< ERROR root missing ns NS2.SCSI.GOV.BY. > > > > <<< ERROR root missing ns SUN.SCSI.GOV.BY. > > > > > > > > CA - ERROR detected in zone .CA > > > > <<< ERROR root missing ns MERLE.CIRA.CA. > > > > <<< ERROR root missing ns RS0.NETSOL.COM. > > > > >>> ERROR delete ns RS0.INTERNIC.NET. from root > > > > > > > > CC - ERROR detected in zone .CC > > > > <<< ERROR root missing ns NS1.LONDON.UK.NETDNS.COM. > > > > >>> ERROR delete ns NS2.GLOBALDNS.COM. from root > > > > > > > > CH - ERROR detected in zone .CH > > > > <<< ERROR root missing ns RIP.PSG.COM. > > > > >>> ERROR delete ns NS.UU.NET. from root > > > > > > > > CI - ERROR detected in zone .CI > > > > <<< ERROR root missing ns MALAKULA.BONDY.IRD.FR. > > > > <<< ERROR root missing ns NS.IRD.FR. > > > > >>> ERROR delete ns MALAKULA.BONDY.ORSTOM.FR. from root > > > > >>> ERROR delete ns NS.RIPE.NET. from root > > > > >>> ERROR delete ns ORSTOM.RIO.NET. from root > > > > > > > > COM - ERROR detected in zone .COM > > > > <<< ERROR root missing ns A.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns B.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns C.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns D.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns E.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns G.GTLD-SERVERS.NET. > > > > <<< ERROR root missing ns I.GTLD-SERVERS.NET. > > > >
[IFWP] Re: Re[2]: Paul Vixie
On Sun, 29 Oct 2000, William X. Walsh wrote: > Hello Joe, > > Sunday, October 29, 2000, 4:40:15 PM, you wrote: > > > institution. At least one things for sure - i have managed to get a bug > > up vixies ass, and that's worth a giggle or two. > > Not really. They post messages from anyone who sends in a lawsuit > threat, regardless of the grounds or who it is. No - not paul. He get's alot of that - I know I keep getting people calling me about pursueing it, or who are pursueing thei own actions. We all know how I can get paul off his proverbial ass. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: Paul Vixie
On Sun, 29 Oct 2000, William X. Walsh wrote: > > Sunday, October 29, 2000, 2:14:03 PM, you wrote: > > > This is great - Vixie has immortalized me ;-) > > > http://mail-abuse.org/lawsuit/baptista.htm > > I see your threat of a lawsuit was as empty as they claimed it would > be. in law william nothing is ever empty - it's just pending. and i'm sure no more nor less pending then you lawsuit threat against this great institution. At least one things for sure - i have managed to get a bug up vixies ass, and that's worth a giggle or two. regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: CDR: [ga] An open letter to Louis Touton (was) www.ester.dyson(fwd)
Hey John - is this guy refering to you? It's a funny sort of compliment. -- Forwarded message -- Date: Sun, 29 Oct 2000 19:41:55 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: CDR: [ga] An open letter to Louis Touton (was) www.ester.dyson At 05:06 PM 10/29/00 -0500, Joe said: > John Palmer is on the right track .. This is the same John Palmer that once tried to unmoderate all of alt.*. I guess age does bring wisdom.
[IFWP] Paul Vixie
This is great - Vixie has immortalized me ;-) http://mail-abuse.org/lawsuit/baptista.htm another resource for the masses ;-) joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] [ga] An open letter to Louis Touton (fwd)
John Palmer is on the right track .. -- Forwarded message -- Date: Sun, 29 Oct 2000 16:04:02 -0600 From: John Palmer <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [ga] An open letter to Louis Touton Mr. Touton, This is to inform you that AGN Domain Name Service, Inc is asserting legals rights to the top level domains .USA, .EARTH and .Z. We have operated a registry for these top-level domains since late 1995. If you check the famous "Postel List", you can see that we were one of the first applicants for new top level domains in late 1995. At that time, we established our registry and have been in operation since that time taking registrations in .EARTH and .USA. In March of 1997, we added the .Z top-level domain. ADNS disagrees with the direction that ICANN is taking the Domain Name System and we do not choose to participate in the ICANN process. Instead, we are supporting alternative root server networks and will continue to do so. Although none of our three top-level domains have been entered into the ICANN application process at this time, we would like to inform you that we are asserting legal ownership of these top level domains. Any attempt to add them to the ICANN controlled root zone under the control and ownership of any other party will be considered by ADNS to be an infringement of our legal rights and we will take appropriate action. For ICANN to assign these top-level domains to another party in the ICANN root would dilute our service mark and damage our company financially. In addition to this, it would also fragment the internet as there would be two different versions of the same top-level domain. In spite of Ms.Dyson's claim, alternative root networks take great care not to allow fragmentation by allowing competing versions of top level domains into their root zones if they are already in existence in another root zone. We would expect ICANN to take the same care and consideration to avoid fragmentation. There is room for all of us on the internet. Please respect our rights to operate our business and respect the rights of alternative root networks. If you have any questions, you can contact me by e-mail. You may consider this an "open letter" and can publish it if you wish. John P. Palmer President AGN Domain Name Service (ADNS), Inc. Chicago, IL
[IFWP] The Internet Namespace Cooperative Root Sync Report Sat Oct 28 23:41:33 EDT 2000
The Internet Namespace Cooperative Root Sync report: Sat Oct 28 23:41:33 EDT 2000 http://www.tinc-org.com/ (c) The dot.GOD Registry @ http://www.dot-god.com/ LA - ERROR detected in zone .LA <<< ERROR root missing ns A.I-DNS.NET. <<< ERROR root missing ns C.I-DNS.NET. <<< ERROR root missing ns E.I-DNS.NET. <<< ERROR root missing ns F.I-DNS.NET. >>> ERROR delete ns AUTH03.NS.UU.NET. from root >>> ERROR delete ns DNSSEC1.SINGNET.COM.SG. from root >>> ERROR delete ns DNSSEC2.SINGNET.COM.SG. from root >>> ERROR delete ns DNSSEC3.SINGNET.COM.SG. from root >>> ERROR delete ns NS.RIPE.NET. from root
[IFWP] Re: Name.Space Root Sync Report Sat Oct 28 22:28:41 EDT 2000
Our friends at namespace should really fix their root soon. Not only is the soa wrong - but alot of errors in the zones. On Sat, 28 Oct 2000, Joe Baptista wrote: > > Name.Space Root Sync report: Sat Oct 28 22:28:41 EDT 2000 > http://www.namespace.org/ > > AT - ERROR detected in zone .AT > <<< ERROR root missing ns NS3.AUSTRIA.EU.NET. > <<< ERROR root missing ns NS7.UNIVIE.AC.AT. > >>> ERROR delete ns ALIJKU01.EDVZ.UNI-LINZ.AC.AT. from root > >>> ERROR delete ns NS.AUSTRIA.EU.NET. from root > > BE - ERROR detected in zone .BE > <<< ERROR root missing ns MASTER.DNS.BE. > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > BO - ERROR detected in zone .BO > <<< ERROR root missing ns AUTH100.NS.UU.NET. > >>> ERROR delete ns WARA.BOLNET.BO. from root > > CA - ERROR detected in zone .CA > <<< ERROR root missing ns MERLE.CIRA.CA. > <<< ERROR root missing ns RS0.NETSOL.COM. > >>> ERROR delete ns RS0.INTERNIC.NET. from root > > CC - ERROR detected in zone .CC > <<< ERROR root missing ns NS1.LONDON.UK.NETDNS.COM. > >>> ERROR delete ns NS2.GLOBALDNS.COM. from root > > CH - ERROR detected in zone .CH > <<< ERROR root missing ns RIP.PSG.COM. > >>> ERROR delete ns NS.UU.NET. from root > > CI - ERROR detected in zone .CI > <<< ERROR root missing ns MALAKULA.BONDY.IRD.FR. > <<< ERROR root missing ns NS.IRD.FR. > >>> ERROR delete ns MALAKULA.BONDY.ORSTOM.FR. from root > >>> ERROR delete ns NS.RIPE.NET. from root > >>> ERROR delete ns ORSTOM.RIO.NET. from root > > COM - ERROR detected in zone .COM > <<< ERROR root missing ns A.GTLD-SERVERS.NET. > <<< ERROR root missing ns B.GTLD-SERVERS.NET. > <<< ERROR root missing ns C.GTLD-SERVERS.NET. > <<< ERROR root missing ns D.GTLD-SERVERS.NET. > <<< ERROR root missing ns E.GTLD-SERVERS.NET. > <<< ERROR root missing ns G.GTLD-SERVERS.NET. > <<< ERROR root missing ns I.GTLD-SERVERS.NET. > <<< ERROR root missing ns M.GTLD-SERVERS.NET. > >>> ERROR delete ns B.ROOT-SERVERS.NET. from root > >>> ERROR delete ns C.ROOT-SERVERS.NET. from root > >>> ERROR delete ns D.ROOT-SERVERS.NET. from root > >>> ERROR delete ns E.ROOT-SERVERS.NET. from root > >>> ERROR delete ns F.ROOT-SERVERS.NET. from root > >>> ERROR delete ns G.ROOT-SERVERS.NET. from root > >>> ERROR delete ns H.ROOT-SERVERS.NET. from root > >>> ERROR delete ns I.ROOT-SERVERS.NET. from root > > DE - ERROR detected in zone .DE > <<< ERROR root missing ns SSS-AT.DENIC.DE. > <<< ERROR root missing ns SSS-NL.DENIC.DE. > >>> ERROR delete ns ADMII.ARL.MIL. from root > >>> ERROR delete ns AUTH61.NS.UU.NET. from root > >>> ERROR delete ns NS.RIPE.NET. from root > > EC - ERROR detected in zone .EC > <<< ERROR root missing ns A.I-DNS.NET. > <<< ERROR root missing ns B.I-DNS.NET. > <<< ERROR root missing ns C.I-DNS.NET. > <<< ERROR root missing ns D.I-DNS.NET. > <<< ERROR root missing ns F.I-DNS.NET. > > FI - ERROR detected in zone .FI > <<< ERROR root missing ns T.NS.VERIO.NET. > >>> ERROR delete ns R2D2.JVNC.NET. from root > > FM - ERROR detected in zone .FM > <<< ERROR root missing ns FM01.FM. > <<< ERROR root missing ns FM03.FM. > <<< ERROR root missing ns NS1.GIP.NET. > <<< ERROR root missing ns NS2.GIP.NET. > <<< ERROR root missing ns NS3.GIP.NET. > <<< ERROR root missing ns SRVR3.RALDEN.COM. > >>> ERROR delete ns DNS.FM. from root > >>> ERROR delete ns DNS2.FM. from root > > GR - ERROR detected in zone .GR > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > GT - ERROR detected in zone .GT > <<< ERROR root missing ns NS.RIPE.NET. > <<< ERROR root missing ns NS.UVG.EDU.GT. > <<< ERROR root missing ns OSI2.GUA.NET. > >>> ERROR delete ns ICM1.ICP.NET. from root > >>> ERROR delete ns NS.GT. from root > >>> ERROR delete ns NS.URL.EDU.GT. from root > >>> ERROR delete ns NS1-AUTH.SPRINTLINK.NET. from root > >>> ERROR delete ns NS2-AUTH.SPRINTLINK.NET. from root > > IE - ERROR detected in zone .IE > <<< ERROR root missing ns ICE.VIA-NET-WORKS.IE. > >>> ERROR delete ns ICE.MEDIANET.IE. from root > > IN - ERROR detected in zone .IN > <<<
[IFWP] Re: i-DNS.net International Root Sync Report Sat Oct 28 22:24:10EDT 2000
Our friends at i-dns should really fix their roots - soon. On Sat, 28 Oct 2000, Joe Baptista wrote: > > i-DNS.net International Root Sync report: Sat Oct 28 22:24:10 EDT 2000 > http://www.i-DNS.net/ > > AL - ERROR detected in zone .AL > <<< ERROR root missing ns ITGBOX.IAT.CNR.IT. > >>> ERROR delete ns ITGBOX.CNUCE.CNR.IT. from root > > AN - ERROR detected in zone .AN > <<< ERROR root missing ns ENGINE1.UNA.NET. > > AT - ERROR detected in zone .AT > <<< ERROR root missing ns NS3.AUSTRIA.EU.NET. > <<< ERROR root missing ns NS7.UNIVIE.AC.AT. > >>> ERROR delete ns ALIJKU01.EDVZ.UNI-LINZ.AC.AT. from root > >>> ERROR delete ns NS.AUSTRIA.EU.NET. from root > > BE - ERROR detected in zone .BE > <<< ERROR root missing ns MASTER.DNS.BE. > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > BO - ERROR detected in zone .BO > <<< ERROR root missing ns AUTH100.NS.UU.NET. > >>> ERROR delete ns WARA.BOLNET.BO. from root > > BY - ERROR detected in zone .BY > <<< ERROR root missing ns NS2.SCSI.GOV.BY. > <<< ERROR root missing ns SUN.SCSI.GOV.BY. > > CA - ERROR detected in zone .CA > <<< ERROR root missing ns MERLE.CIRA.CA. > <<< ERROR root missing ns RS0.NETSOL.COM. > >>> ERROR delete ns RS0.INTERNIC.NET. from root > > CC - ERROR detected in zone .CC > <<< ERROR root missing ns NS1.LONDON.UK.NETDNS.COM. > >>> ERROR delete ns NS2.GLOBALDNS.COM. from root > > CH - ERROR detected in zone .CH > <<< ERROR root missing ns RIP.PSG.COM. > >>> ERROR delete ns NS.UU.NET. from root > > CI - ERROR detected in zone .CI > <<< ERROR root missing ns MALAKULA.BONDY.IRD.FR. > <<< ERROR root missing ns NS.IRD.FR. > >>> ERROR delete ns MALAKULA.BONDY.ORSTOM.FR. from root > >>> ERROR delete ns NS.RIPE.NET. from root > >>> ERROR delete ns ORSTOM.RIO.NET. from root > > COM - ERROR detected in zone .COM > <<< ERROR root missing ns A.GTLD-SERVERS.NET. > <<< ERROR root missing ns B.GTLD-SERVERS.NET. > <<< ERROR root missing ns C.GTLD-SERVERS.NET. > <<< ERROR root missing ns D.GTLD-SERVERS.NET. > <<< ERROR root missing ns E.GTLD-SERVERS.NET. > <<< ERROR root missing ns G.GTLD-SERVERS.NET. > <<< ERROR root missing ns I.GTLD-SERVERS.NET. > <<< ERROR root missing ns M.GTLD-SERVERS.NET. > >>> ERROR delete ns B.ROOT-SERVERS.NET. from root > >>> ERROR delete ns C.ROOT-SERVERS.NET. from root > >>> ERROR delete ns D.ROOT-SERVERS.NET. from root > >>> ERROR delete ns E.ROOT-SERVERS.NET. from root > >>> ERROR delete ns F.ROOT-SERVERS.NET. from root > >>> ERROR delete ns G.ROOT-SERVERS.NET. from root > >>> ERROR delete ns H.ROOT-SERVERS.NET. from root > >>> ERROR delete ns I.ROOT-SERVERS.NET. from root > > CZ - ERROR detected in zone .CZ > <<< ERROR root missing ns CZ.EUNET.CZ. > <<< ERROR root missing ns NS2.NIC.FR. > >>> ERROR delete ns NS.CESNET.CZ. from root > >>> ERROR delete ns NS.EUNET.CZ. from root > > DE - ERROR detected in zone .DE > <<< ERROR root missing ns SSS-AT.DENIC.DE. > <<< ERROR root missing ns SSS-NL.DENIC.DE. > >>> ERROR delete ns ADMII.ARL.MIL. from root > >>> ERROR delete ns AUTH61.NS.UU.NET. from root > >>> ERROR delete ns NS.RIPE.NET. from root > > EC - ERROR detected in zone .EC > <<< ERROR root missing ns A.I-DNS.NET. > <<< ERROR root missing ns B.I-DNS.NET. > <<< ERROR root missing ns C.I-DNS.NET. > <<< ERROR root missing ns D.I-DNS.NET. > <<< ERROR root missing ns F.I-DNS.NET. > > FI - ERROR detected in zone .FI > <<< ERROR root missing ns T.NS.VERIO.NET. > >>> ERROR delete ns R2D2.JVNC.NET. from root > > FM - ERROR detected in zone .FM > <<< ERROR root missing ns FM01.FM. > <<< ERROR root missing ns FM03.FM. > <<< ERROR root missing ns NS1.GIP.NET. > <<< ERROR root missing ns NS2.GIP.NET. > <<< ERROR root missing ns NS3.GIP.NET. > <<< ERROR root missing ns SRVR3.RALDEN.COM. > >>> ERROR delete ns DNS.FM. from root > >>> ERROR delete ns DNS2.FM. from root > > GR - ERROR detected in zone .GR > <<< ERROR root missing ns NIC.AIX.GR. > >>> ERROR delete ns SPARKY.ARL.MIL. from root > > GT - ERROR detected in zo
[IFWP] ester - what's up
There's alot of ester dyson in the air these days. she's managed to piss off a whole group of cypherpunks - go figure. The lists are alive with ester these days - and non of it very good. She's been spamming the cypherpunks. Not a good idea. Almost reminds me of a technological version of the good old roman days, the days of empire. The lions are in the ring, circling and hungry - and there's ester all ready for dinner. And I wonder if she knows she's the dinner. -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] Re: Dealing with Spam from Esther Dyson
Tim - you have to understand that Esther is trying to remain relevant in a world that increasingly sees her as last years meat rack. Ester knowns me, in fact she spent most of her last trip to Cairo trying to convence lawyers that I should be sued for something. She blames me for scaring off president Mubarak from the ICANN show. The woman is unfortunately paranoid and suffers from persecution dementia. Someday someone may wright a comedy on the lady, I consider it more tragedy. I think Ester would of been happier in life being a common housewife - or dominatrix. Unfortunately she was born into the Dyson clan and as a result has always been pushed to excell. But that has not been the case. On a technological front she is all show - no substance. And that show started early in life. She herself can confirm that her schooling at harvard was for no other purpose then socialization. I think meeting the right people was her angle for attendance. I understand her venture capital positions have mainly failed, her chairmanship of ICANN has been an absolute disaster. She's being disposed as the chair this november - that does not mean ICANN will be a better place - just less blond. She's not a blond you know - but she certainly has disposition of one. But alas Tim - I like her. I think she's sexy in her own special way. Ol gals ya know have some of the softtest skin ;-) Joe On Fri, 27 Oct 2000, Tim May wrote: > > By the way, a few minutes with Google turned up other instances of > Esther Dyson's spamming. > > Here's just one such URL, along with the opening paragraphs: > > http://channel.nytimes.com/1998/03/28/technology/28dyson.html > > March 28, 1998 > > I Got Spammed by Esther Dyson: > Release, the Old-Fashioned Way > > By LISA NAPOLI > ecently, I got a note from the publisher of Release 1.0, the > venerable newsletter put out by the venerable (and mythic) godmother > of all things digital, Esther Dyson. > > It wasn't a casual e-mail. It wasn't a letter asking me to write for > the newsletter. It wasn't even a personal note asking me to have > lunch, or attend her annual conference (which took place this week in > Tucson, where, for the first time, non-Release subscribers were > permitted to attend.) > > The note was plain old-fashioned snail mail spam, asking me to fork > over nearly 700 bucks for a subscription. > > Dear Lisa, > > Esther Dyson and Jerry Michalski believe that someone who's achieved > your stature in our industry should be part of the Release 1.0 > family. That's why they've suggested I write this letter to you. > > > Stature? How did they measure that? Did Jerry Michalski remember > sitting at the same table with me at a conference luncheon once? Did > Esther ever read my now deceased column, Hyperwocky? Did some > computer notice my name on all those mailing lists? > -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Re: Dealing with Spam from Esther Dyson
I missed this. Can you or anyone please forward to me the spam Ester sent you. I know the old crow and i'm sure there are some people on domain policy who would love to read her spam. regards joe On Fri, 27 Oct 2000, R. A. Hettinga wrote: > At 6:47 PM -0700 on 10/27/00, Tim May wrote: > > > > So, Esther Dyson, whom I have never corresponded with, is spamming me > > with this crap. > > Me too. > > Maybe her people just learned about the majordomo "who" command... > > Cheers, > RAH > Clueless is as, etc... > -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster
[IFWP] Palestine & DNS DDOS Attacks - pending
Recently Palestinian hackers have responded to an israeli hacker distributed denial of service attack against a palestinian web site by launching DDOS attacks against israeli sites. It would be interesting to see if the palestinians attack the israeli country code domain .il - they certainly would do more damage if they attacked the israeli cctld dns servers. All israeli sites would end up disappearing from the internet. Of course a simular attack could be launched against the USG roots for a bigger bang - but it would be a slightly more difficult task. According to dig - which see attached printout - the isralis operate their primary servers at The Hebrew University of Jerusalem and Tel-Aviv University. They also have secondary service via RIPE, PSGnet (Randy Bush) and NAP. RIPE might require some effort to take out, but with a good DDOS and several million dns spoofs would take the israeli cctld offline. It's a good thing no one on the arab side has figured it out yet. ipip:~# dig @ARISTO.TAU.AC.il. il. soa ; <<>> DiG 8.2 <<>> @ARISTO.TAU.AC.il. il. soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6 ;; QUERY SECTION: ;; il, type = SOA, class = IN ;; ANSWER SECTION: il. 1D IN SOA relay.huji.ac.il. bindmaster.relay.huji.ac.il. ( 2000102601 ; serial 1D ; refresh 4H ; retry 6W ; expiry 1D ); minimum ;; AUTHORITY SECTION: il. 1D IN NSrelay.huji.ac.il. il. 1D IN NSaristo.tau.ac.il. il. 1D IN NSns.ripe.net. il. 1D IN NSns2.nap.net. il. 1D IN NSrip.psg.com. ;; ADDITIONAL SECTION: relay.huji.ac.il. 1D IN A 128.139.6.1 aristo.tau.ac.il. 1D IN A 132.66.32.10 ns.ripe.net.3h19m6s IN :::193.0.0.193 ns.ripe.net.1d13h47m41s IN A 193.0.0.193 ns2.nap.net.1d13h47m46s IN A 206.54.224.1 rip.psg.com.1d13h47m52s IN A 147.28.0.39 ;; Total query time: 241 msec ;; FROM: ipip to SERVER: ARISTO.TAU.AC.il. 132.66.32.10 ;; WHEN: Fri Oct 27 18:25:18 2000 ;; MSG SIZE sent: 20 rcvd: 300 regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Streamlining Domain Squabbles
Streamlining Domain Squabbles (Politics 2:00 a.m. PDT) http://www.wired.com/news/politics/0,1283,39591,00.html?tw=wn20001026 Websites preparing to do battle over ownership of domain names have new tools to help build their cases. Several groups are organizing the arbitration results so that arguments can be cited. By Oscar S. Cisneros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] I-DNS
I've recently written a sync program to keep non USG roots in sync with legacy tld data. And while I was doing so - I noticed I-DNS recently started providing dns service to cctld .ec (ecuador) and just today they started doing dns for .la (laos). -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] A little Jeff Williams in the morning goes a long way
Did'nt know this was there http://www.ntia.doc.gov/ntiahome/domainname/proposals/ineginc/ineginc.htm regards joe -- Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Can you see GOD?
If you can see the GOD top level domain zone and can help me test some virtual host redirects for our parked domain owners - please visit http://www.dot-god.com/beta/1/redirects/ Our domain owners have parked about 4,500 domains with us and I am testing to see if we can support that number of virtual hosts on one IP. Looks like we can. All parked dot.god domains are being redirected to their respective whois record. Thanks in advance for your assistance. P.S. If you want to see GOD - visit www.youcann.org for details. dot.GOD Hostmaster http://www.dot-god.com/ [EMAIL PROTECTED]
[IFWP] [ga] Poorman's Web Cast (fwd)
--
Joe Baptista
http://www.dot.god/
dot.GOD Hostmaster
+1 (805) 753-8697
-- Forwarded message --
Date: Fri, 20 Oct 2000 15:18:23 -0700
From: Bret A. Fausett <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [ga] Poorman's Web Cast
For those who are interested in a web cast of yesterday's Names Council
meeting, I'm provided a poorman's version on my web site. You can get it
here: http://www.lextext.com/nc1019.html
Consider this 'proof of concept' for how to do this cheaply in the future.
It's not real time, but Names Council meetings are not open to public
participation anyway. I had this up within an hour after the close of
yesterday's meeting.
You'll need the ability to listen to mp3 files. Depending on your browser
client, plug-ins, and bandwidth, it may stream.
Anyone who listens, please provide feedback on the technical issues.
Hopefully, this will show the Names Council how to webcast its monthly
meetings in the future in a cost effective manner.
-- Bret
--
This message was passed to you via the [EMAIL PROTECTED] list.
Send mail to [EMAIL PROTECTED] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html
[IFWP] dot.KIDS tld applications
I'm still waiting for all the dot.KIDS applications to be online - so far the applications submitted by DotKids, Inc. and .KIDS Domains, Inc. fail my safe kids test. These people are dreaming in technocolor - but playing on a Black & White landscape. First of all - let me say I do not support an application for .KIDS in the USG namespace. .KIDS already exists and as far as i'm concerned the US government is a criminal tresspasser. However - I was interested in the application and if any of the .KIDS hopefulls had any idea of what they are doing. The application are all together lame - and speak of internet visionaries and other such marketing stuff - but non approached the issues of making the tld "safe" for kids. In both of the above cases these people are subcontracting the function hopefully to others. Won't work - especially at the rates to registrar that DotKids, Inc. proposes ($12.00). Impossible at those fees. A safe registry has to be vigilent in verifying and ensuring safe content. This is a very expensive process which non of these proposals addresses. This will of course ensure abuse of the registry, there simply won't be the finance to police the registry. These people have spent alot of cash on drafting the technicals and have forgotten the practicles. I look forward to reviewing the other submissions. Regards Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] ICANN NEWS
ICANN Elects Iconoclasts (Politics 3:00 a.m. PDT) http://www.wired.com/news/politics/0,1283,39385,00.html?tw=wn20001012 At least two of the five new officers for the Internet's governing body are staunch and outspoken critics of the way the organization has been run in the past. Declan McCullagh reports from Washington. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ICANN Gets Five New Members (Politics Wednesday) http://www.wired.com/news/politics/0,1283,39384,00.html?tw=wn20001012 In a highly watched cyberelection, longtime Internet policy critic Karl Auerbach wins one of five spots as representatives to ICANN. Among the losers: law professor and author Lawrence Lessig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Brazilian Tribe Gets 'Squatted
Brazilian Tribe Gets 'Squatted (Politics Monday) http://www.wired.com/news/politics/0,1283,39354,00.html?tw=wn20001010 The Yanomami, a well-documented, primitive tribe in the Amazon, discovers that its name has become a dot-com. Somebody's trying to sell the domain for $25K, and the tribe's none too happy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] I-D ACTION:draft-hollenbeck-grrp-reqs-05.txt (fwd)
--- begin forwarded text Date: Wed, 10 Oct 2000 06:39:00 -0500 (EST) To: ietf-announce: ; Subject: I-D ACTION:draft-hollenbeck-grrp-reqs-05.txt From: [EMAIL PROTECTED] A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Generic Registry-Registrar Protocol Requirements Author(s) : S. Hollenbeck Filename: draft-hollenbeck-grrp-reqs-05.txt Pages : 23 Date: 09-Oct-00 This document describes high-level functional and interface requirements for a client-server protocol for the registration and management of Internet domain names in shared Top Level Domain (TLD) registries. Specific technical requirements detailed for protocol design are not presented here. Instead, this document focuses on the basic functions and interfaces required of a protocol to support multiple registry and registrar operational models. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hollenbeck-grrp-reqs-05.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-hollenbeck-grrp-reqs-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: [EMAIL PROTECTED] In the body type: "FILE /internet-drafts/draft-hollenbeck-grrp-reqs-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <[EMAIL PROTECTED]> ENCODING mime FILE /internet-drafts/draft-hollenbeck-grrp-reqs-05.txt <ftp://ftp.ietf.org/internet-drafts/draft-hollenbeck-grrp-reqs-05.txt> --- end forwarded text Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Inching Toward Dot-Whatever
Inching Toward Dot-Whatever (Business 3:00 a.m. PDT) http://www.wired.com/news/business/0,1367,39246,00.html?tw=wn20001004 As the ICANN deadline for proposing new top-level domains closes, Network Solutions and other domain big-wigs pitch their ideas for new Internet name endings. By Chris Oakes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] No Porn Wanted at .Kids
No Porn Wanted at .Kids (Business 3:00 a.m. PDT) http://www.wired.com/news/business/0,1367,39169,00.html?tw=wn20001002 A company wanting to become the registrar of family-friendly domains - - where only porn-free websites would roam free -- has applied to ICANN to operate the .kids top-level domain. By Oscar S. Cisneros. Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Vint Cerf and Robert Kahn defend Al Gore (fwd)
i noticed this article on friday but it never made it to the dns groups and it's somewhat relevant. -- Forwarded message -- Date: Fri, 29 Sep 2000 11:15:55 -0400 From: Declan McCullagh <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Vint Cerf and Robert Kahn defend Al Gore http://www.cluebot.com/article.pl?sid=00/09/29/0711253&mode=thread Did Al Gore Really Invent the Internet? posted by cicero on Friday September 29, @02:11AM from the resuscitating-al-gore's-image dept. As the election nears, Net-pioneers Vint Cerf and Robert Kahn are busy defending Al Gore. The veep's invented-here crack about creating the Internet, they claim in their article attached below, has been terribly misunderstood. Now, we're fans of the TCP/IP-inventing duo, but it's been a long time in political ecology since Cerf famously joked 15 years ago in parody RFC968 that: "Twas the night before start-up and all through the net, not a packet was moving; no bit nor octet..." Things are more complicated now, and MCI's Cerf has morphed from an IETF geek into a Washington powerbroker and Friend of Bill and Al. Cerf showed up at the New Year's Eve White House millennium gala, spoke at an October 1999 White House "Millennium Evening" lecture, and appeared with the president and vice president at a July 1997 event to introduce administration policy proposals. We note that other prominent figures recently have made similar attempts to rescue Gore's tattered image among techies. But a more neutral description of the vice president's role in history is, we think, a fine 1999 article by author Virginia Postrel. Their article: http://www.cluebot.com/article.pl?sid=00/09/29/0711253&mode=thread
[IFWP] anglicans on domain space
http://anglicansonline.org/
[IFWP] Re: A day in the life of dot.COM (fwd)
some of my replies regarding dot.com -- Forwarded message -- Date: Fri, 22 Sep 2000 10:00:02 -0400 (EDT) From: Joe Baptista <[EMAIL PROTECTED]> To: Chuck Hatcher <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: A day in the life of dot.COM PEOPLE - one important thing I forgot to address in my posting of all that data. For reason reason the sales and cancellation figures do not include dot.com names beginning with K. I made a programming booboo and ended up loosing letter K. On Fri, 22 Sep 2000, Chuck Hatcher wrote: > That's very interesting reading - thanks for sharing it with us. I do have > a few questions: > > 1. What do you mean by "2723 (approx. $10,000 in sales)" ? Why wouldn't > 2723 be $27,230 in sales, not accounting for rebates? Or do you mean gross > profit, after paying the registry? net profit, after paying the registry and prior to any rebates - I assumed $4.00 / domain name net profit. > 2. What do you mean by Cancel? Do you mean deleted from the shared > registry, or dropped from the zone files? Big difference, as far as I'm > concerned. If it means dropped from the zone files, does that mean > re-appearance in the zone file will show up in Sales (for instance renewals > paid after the domain is placed on hold)? If so NSI Sales is not really all > "new" sales, but includes some renewals? Hypothetically, if every other day > I remove the name servers on all my OpenSRS domains, then the next day put > them back, will I distort your figures? Please note, I'm not trying to find > flaws in your work, I'm just trying to understand it. I'm aware of that. By canceled I mean it was removed from te zone file but is still in the whois file. I consider that an overdue account receivable - but there's simply not enough information to estimate what are NEW sales and what are PAID outstanding due Account receivable. To do that I have to track it by domain - which is what i'm working on. > > 3. How do you determine how many domains were registered by a particular > registrar? Are you running whois lookups on zone file drops and adds? exactly. names dropped from the zone file or added to the zone file are xcross referenced to the registrar via the registry whois. > Looking at the big picture (from a one-day snapshot), NSI (registrar) is not > only losing market share, but is a net loser of registrations in total. > (Question: How long until the number of domains NSI manages decreases to the > point that they can provide decent customer service to their remaining > customers?) yup - i have to agree and have already addressed this to network solutions. > > I wonder what the story behind the 15 OpenSRS "Cancels" is? Are they all > transfers to other registrars? Or deleted name servers? Or deletions on > request? Or by UDRP decision? Or what else? > > Again, thanks for the report. > > Chuck Hatcher > > - Original Message - > From: "Joe Baptista" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 22, 2000 8:03 AM > Subject: A day in the life of dot.COM > > > > > > As you all know - I have an interest in following the growth of > > dot.com. I used to get the dot.com data from third particies since my > > main interest is in the numbers and not the area of speculation. So I now > > > pick up the files myself and have been developing a tracking system for > > dot.com. At this time I'm experimenting with the dot.com file for Sep 18 > > and Sep 19, 2000 and have some interesting comparisons for domain sales > > and cancelations for Sep 19 2000, which i've listed below. According to > > these figures Tucows created some 2723 (approx. $10,000 in sales). The > > top ten registrars for that day have been listed first. > > > > Sales Cancel Registrar > > === === > > 20876 31421 NETWORK SOLUTIONS, INC. > >4926 54 REGISTER.COM, INC. > >3875 0 DOTSTER, INC. > >2723 15 TUCOWS.COM, INC. > >2048 30 BULKREGISTER.COM, INC. > >1208 5 ENOM, INC. > >1180 5 CORE INTERNET COUNCIL OF REGISTRARS > > 984 13 MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE > > 366 13 INTERNET DOMAIN REGISTRARS > > 300 0 SCHLUND+PARTNER AG > > > > 15 0 1STDOMAIN.NET, DIVISION OF G+D INTERNATIONAL LLC > > 46 0 ABACUS AMERICA, INC. DBA NAMES4EVER > > 36 1 ALL WEST COMMUNICATIONS, INC. D/B/A AW REGISTRY > > 60 0 ALLDOMAINS.COM INC. > > 3 0 BB ONLINE UK LTD > > 1
[IFWP] A day in the life of dot.COM
As you all know - I have an interest in following the growth of dot.com. I used to get the dot.com data from third particies since my main interest is in the numbers and not the area of speculation. So I now pick up the files myself and have been developing a tracking system for dot.com. At this time I'm experimenting with the dot.com file for Sep 18 and Sep 19, 2000 and have some interesting comparisons for domain sales and cancelations for Sep 19 2000, which i've listed below. The top ten registrars for that day have been listed first in order of sales volumn. I don't have enough data yet to make any predictions. But I speculate, based on this data dump and other I've done over the month, that network solutions is in some degree of difficulty. Most of the time their accounts recievable and due (being cancellations) exceeds daily sales. This is not a good thing and if netsol does not improve it's position and this sort of thing continues their financial viability is in question. I can also speculate that their are a few registrars out there who are on the way to bankruptcy. Sales Cancel Registrar === === 20876 31421 NETWORK SOLUTIONS, INC. 4926 54 REGISTER.COM, INC. 3875 0 DOTSTER, INC. 2723 15 TUCOWS.COM, INC. 2048 30 BULKREGISTER.COM, INC. 1208 5 ENOM, INC. 1180 5 CORE INTERNET COUNCIL OF REGISTRARS 984 13 MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE 366 13 INTERNET DOMAIN REGISTRARS 300 0 SCHLUND+PARTNER AG 15 0 1STDOMAIN.NET, DIVISION OF G+D INTERNATIONAL LLC 46 0 ABACUS AMERICA, INC. DBA NAMES4EVER 36 1 ALL WEST COMMUNICATIONS, INC. D/B/A AW REGISTRY 60 0 ALLDOMAINS.COM INC. 3 0 BB ONLINE UK LTD 1 0 CAPITAL NETWORKS PTY LTD 17 0 CATALOG.COM, INC. 211 1 DOMAIN BANK, INC. 25 0 DOMAIN REGISTRATION SERVICES 28 0 DOMAININFO AB 155 0 DOMAINPEOPLE, INC. 17 0 DOMAINREGISTRY.COM 6 0 E-NAMES.ORG 3 0 EASTERN COMMUNICATIONS CO., LTD. 228 1 EASYSPACE LTD 17 0 EPAG ENTER-PRICE MULTIMEDIA AG 14 0 FRANCE TELECOM/TRANSPAC 48 0 G.K. GROUP, L.L.C. 279 0 GANDI 83 0 HANGANG SYSTEMS, INC. D/B/A DOREGI.COM 51 0 IBI CO., LTD. 186 0 IHOLDINGS.COM, INC. D/B/A DOTREGISTRAR.COM 92 0 INNERWISE, INC. D/B/A ITSYOURDOMAIN.COM 1 0 INTERACCESS CO. 69 0 INTERQ, INC. 1 0 NAMEBAY 67 0 NAMESDIRECT.COM, LTD 156 0 NAMESECURE.COM 16 0 NORDNET 58 0 ONLINENIC, INC. D/B/A CHINA-CHANNEL.COM 5 0 PARAVA NETWORKS, INC. 2 0 PSI-JAPAN, INC. 4 0 SECURA GMBH 11 0 SIGNATURE DOMAINS, INC. 35 0 SPEEDNAMES, INC. 9 0 STARGATE COMMUNICATIONS, INC. 28 0 THE NAME IT CORPORATION 7 0 THE REGISTRY AT INFO AVENUE 141 5 TIERRANET, INC. 15 6 XIN NET CORP. 24 0 YESNIC === === 52630 31644 TOTALS dot.GOD Hostmaster http://www.dot-god.com/ [EMAIL PROTECTED]
[IFWP] Dot.web news
Some Dots Can't Be Trademarked (Politics 3:00 a.m. PDT) http://www.wired.com/news/politics/0,1283,38826,00.html?tw=wn2918 An alternative registry operator plans to appeal a judge's ruling that .web cannot be trademarked. Others want generic top-level domains to remain generic. By Oscar S. Cisneros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Re: NASA (and e.root-servers.net) off the air (fwd)
-- Forwarded message -- Date: Fri, 15 Sep 2000 15:23:52 -0400 From: Mark A Gebert <[EMAIL PROTECTED]> To: Chris Adams <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: NASA (and e.root-servers.net) off the air AMES has been under a DOS attack for most of the day --geeb - Mark A. Gebert Email: [EMAIL PROTECTED] Senior Research Programmer Voice:+1 734 936 2655 Merit Network, Inc Fax: +1 734 647 3185 4251 Plymouth Rd, Suite C, Ann Arbor, MI 48105-2785 - If I show up at your door step, you probably did something to bring me there % cat std.disclaimers At 14:05 -0500 15 September 2000, Chris Adams wrote: > > It appears that all of NASA, including e.root-servers.net at Ames, is > off the net (and has been most of the day). I've heard something about > them having some kind of trouble at MAE-EAST and MAE-WEST; does anybody > know anything more than that? > -- > Chris Adams <[EMAIL PROTECTED]> > Systems and Network Administrator - HiWAAY Information Services > I don't speak for anybody but myself - that's enough trouble. --
[IFWP] NASA (and e.root-servers.net) off the air (fwd)
-- Forwarded message -- Date: Fri, 15 Sep 2000 14:05:42 -0500 From: Chris Adams <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: NASA (and e.root-servers.net) off the air It appears that all of NASA, including e.root-servers.net at Ames, is off the net (and has been most of the day). I've heard something about them having some kind of trouble at MAE-EAST and MAE-WEST; does anybody know anything more than that? -- Chris Adams <[EMAIL PROTECTED]> Systems and Network Administrator - HiWAAY Information Services I don't speak for anybody but myself - that's enough trouble.
[IFWP] Re: The BIND 2000 survey
thanks jeff - and i just noticed the data was not nicely lined up. ops. but as you can see - growth of dns servers is soaring. dot.GOD Hostmaster http://www.dot-god.com/ [EMAIL PROTECTED] On Sat, 9 Sep 2000, Jeff Williams wrote: > Joe and all, > > Joe, thank you for this very useful information. I am sure that > Esther and Becky will be pleased as punch/latex(Red??) > > !Dr. Joe Baptista wrote: > > > I've just downloaded the most recent com net org and edu zone files and > > have extracted the nameserver records for each. > > > > Zone Number of DNS > > YR 2000 YR 1999 % Growth > > com 284487 134333 111.8 > > edu 7218 650610.9 > > net 172189? ? > > org 135419 61739 119.3 > > Totals 599313 > > > > The net number of servers for the above zones is 317504 (net of duplicates). > > > > Last year the BIND 1999 survey discovered 134333 servers in the .com zone, > > 6506 in the .edu zone and 61739 in the .org zone. > > > > the .com and .org zones have grown by over 110%. > > > > regards > > joe > > > > Joe Baptista > > The dot.GOD Registry > > http://www.dot.god/ > > > > --- > > You are currently subscribed to ncdnhc-discuss as: [EMAIL PROTECTED] > > To unsubscribe send a blank email to [EMAIL PROTECTED] > > Regards, > > -- > Jeffrey A. Williams > Spokesman INEGroup (Over 112k members strong!) > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > Information Network Eng. Group. INEG. INC. > E-Mail [EMAIL PROTECTED] > Contact Number: 972-447-1800 x1894 or 9236 fwd's to home ph# > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > >
[IFWP] CNRP
I have a feeling this wont ever fly - but USER-FRIENDLY ALTERNATIVE TO URLS DUE SOON Technology that permits users to access Internet sites, locate information, and send emails using simple and easily remembered names instead of URLs is coming close to completion and is entering the market. Engineers at Network Solutions, RealNames, Netword, and AT&T have developed the Common Names Resolution Protocol (CNRP). A beta version of NSI's CNRP software is being released for Web users, and later this fall RealNames and Netword will offer commercial CNRP versions. CNRP will likely be useful in the wireless environment due to its use of short and simple phrases and names, and network managers at corporations could utilize CNRP services to access employee and customer information or to share corporate documents. This month a final version of the CNRP protocol specification will be published and this fall the Internet Engineering Task Force (IETF) will probably approve CNRP as a standards-track protocol. Internationalized domain names are the final technical obstacle CNRP faces, says Leslie Daigle, chair of the IETF working group on CNRP. The current CNRP pilot project will run for approximately six months. (Network World, September 4 2000) Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] The BIND 2000 survey
I've just downloaded the most recent com net org and edu zone files and have extracted the nameserver records for each. Zone Number of DNS YR 2000 YR 1999 % Growth com 284487 134333 111.8 edu 7218 650610.9 net 172189? ? org 135419 61739 119.3 Totals 599313 The net number of servers for the above zones is 317504 (net of duplicates). Last year the BIND 1999 survey discovered 134333 servers in the .com zone, 6506 in the .edu zone and 61739 in the .org zone. the .com and .org zones have grown by over 110%. regards joe Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Re: [ga] ICANN ELECTIONS - DIRECTORS - NOMINATIONS (fwd)
Hello Jeanette
First of all I would like to make clear that a fluffer is not a derogitive
term. A fluffer is a valuable professional and the state of California
agrees and provides a registry for them. Indeed if we only had a registry
for ICANN fluffers it would certainly make my job a lot easier.
Furthermore the association I make between an ICANN fluffer and a
professional is not per say so much in the act as it is in the practice and
net results.
In order to understand this we must first understand the mechanics of
fluffing. We begin by examing the definition which will also serve to
satisfy your first query.
Fluffer (def.) a professional practicioner {male or female} of the erotic
art of fellatio. Fluffers are frequently hired by the porn industry to
assist male actors in maintaining a firm resolve during the rigorous
performance for the cinematic beast. As a rule the fluffer maintains
firmness in the fluffey without ever achieving a climax or orgasm.
I am sure you will now agree with me that there is nothing at all
derogatory in that. Indeed I can confirm that 9 out of 10 men preffer
fluffers and most married men would - if given an opportunity - replace
their wives with a fluffer. Indeed I can say with considerable pride that
I have from time to time enjoyed a fluffer or two - and it was
good. Indeed fluffers are an integrale part of human society - and
thank.God for that.
Now an ICANN fluffer performs much in the same way as a proffessional
fluffer - minus the pleasure. They lie, cheat, and steal while making soft
cooing noises of love. Ester Dyson is an excellent example of an ICANN
fluffer.
Now - you have been assigned the ICANN fluffer title for the following reasons.
1) No trusted party in the domain industry has validated you. No one knows
who you are, and
2) You associate with the wronq people.
and thats that.
Now - I will be contacting you in the near future with a list of questions
on behalf of my dot.God domain owners. I can assure you that my personal
opinion will not be expressed to them. Only our discussion will be
indexed, and participation is of course optional and at your descretion.
regards
joe
>Hi, you use the term fluffer several times. None of my dictionaries
>knows the verb to fluffer. However, I get the sense that is negatively
>connotated. Would you be so kind to tell me if this is true?
>jeanette
>
>>Latin America
>>--
>>-Claudio Silva Menezes ([EMAIL PROTECTED])
>> I smell an ICANN fluffer but not sure. Possible association with
>>Roberto Gato and Hitler Sola.
>>North America
>>---
>>-Karl Auerbach ([EMAIL PROTECTED])
>> Good guy.
>>-Barbara Simons ([EMAIL PROTECTED])
>> OK.
>>-Emerson Tiller ([EMAIL PROTECTED])
>> ICANN fluffer - Trademark flunky.
>>Regards
>>Joe
>>Joe Baptista
>>The dot.GOD Registry
>>http://www.dot.god/
>>
>>--
>>This message was passed to you via the [EMAIL PROTECTED] list.
>>Send mail to [EMAIL PROTECTED] to unsubscribe
>>("unsubscribe ga" in the body of the message).
>>Archives at http://www.dnso.org/archives.html
>>
Joe Baptista
The dot.GOD Registry
http://www.dot.god/
[IFWP] More Ester Polyester quotes
QUOTE OF THE DAY: "From the beginning we had to deal with the notion of some people that we were giving away an American birthright to foreigners." -- Esther Dyson, outgoing ICANN chair, recaps some of the organization's early growing pains Read it here --> http://www.techinformer.com/go.cgi?id=310807 Joe Baptista The dot.GOD Registry http://www.dot.god/
Re: [IFWP] Re: Root zone change --- Informational Message
thank you william - my heart is better now. Sorry folks - everyone go back to sleep. my mistake. regards dot.GOD Hostmaster http://www.dot-god.com/ [EMAIL PROTECTED] On Fri, 8 Sep 2000, William X. Walsh wrote: > Hello !Dr., > > Friday, September 08, 2000, 2:50:53 PM, you wrote: > > > This is horrifying - one week? There are some 600,000 dns servers on the > > internet most of whom (99.7%) carry the root.cache file which contains the > > old k root server. And you guys want turn it off in a week. That's a > > very lame thing to do. > > Uh, Joe, this is the k.gtld-servers.net server. The root.cache files > will not be effected. > > -- > Best regards, > Williammailto:[EMAIL PROTECTED] > >
[IFWP] Re: Root zone change --- Informational Message
This is horrifying - one week? There are some 600,000 dns servers on the internet most of whom (99.7%) carry the root.cache file which contains the old k root server. And you guys want turn it off in a week. That's a very lame thing to do. regards Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697 On Fri, 8 Sep 2000, Verd, Brad wrote: > > Informational Message: > > The IP for k.gtld-servers.net will be changed in the authoritative list for > .com, .net, and .org. Changes will be reflected in the zone with serial > number 290801 > > The old IP for k.gtld-servers.net is 195.8.99.11 and the new IP is > 213.177.194.5 > > The old server will remain in service for a minimum of a week. > > -- > Brad Verd > gTLD Operations Manager > Network Solutions Registry > Email - [EMAIL PROTECTED] > --- >
[IFWP] ICANN Directors Nominations (follow up)
859 3.7%
EUROPE Jeanette HofmannN 11855.1%
EUROPE Dmitri Bourkov N Add 536 2.3%
LATAMER Claudio Silva Menezes N 865 24.3%
NRAMER Karl Auerbach N 575 5.4%
NRAMER Barbara Simons N 429 4.0%
NRAMER Emerson Tiller N 373 3.5%
Notes on NFlag: N (Nominated)
N Add (Nominated and added later)
regards
Joe Baptista
http://www.dot.god/
dot.GOD Hostmaster
+1 (805) 753-8697
[IFWP] AUCTION CHINESE DOT-COMS
MINISTRY TO AUCTION CHINESE DOT-COMS http://www.idg.net/go.cgi?id=308675 Joe Baptista The dot.GOD Registry http://www.dot.god/
[IFWP] Re: [Random-bits] Network Solutions' Common Name Resolution Protocol
This is cut. Apart from the fact that it's garbage, the site certificates don't work. They have been signed over to research.netsol.com and some browsers will warn you that the issueing computer is not the connected computer. Maybe network solution might want to fix this. regards Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697 On Mon, 4 Sep 2000, James Love wrote: > Network Solutions' Common Name Resolution Protocol > > The text below is from: > > http://cnrp.research.netsol.com/ > > So just what is CNRP? > > The Common Name Resolution Protocol allows you to send queries and > receive results for a specific set of things that we call Common Names. > Common Names (CNs) are names that are engineered to behave the way human > beings use names. > > For example, people are perfectly comfortable with two different > things being called the same thing. When we say something about "Joe > Smith" we don't worry about the fact that there are probably several > thousand Joe Smiths in the world. We know that we're probably limiting > the scope of our discussion to some known understood geographic area or > circle of friends. > > On the Internet the names that have been used to date are all > engineered to make life easy for the machines. We as humans don't need > dots, dashes, squiggles and colons to be able to get by. So why should > we have to conform to the machines? Why can't we get them to handle > names for things the way we do normally? > > That's where common-names come into play. CNs have three > attributes that ordinary Internet names such as email addresses and URLs > don't have: non-uniqueness, parameterization and an unlimited character > set. Those big words just mean that > > 1.Non-uniqueness -- two objects can have the same name. > > This means that very often when you use a common-name you will > be asked which one out of a list is the one you are really looking for. > > 2.Parameterization -- a common-name query can include other > information such as the location, topic or language you happen to be > interested in. > > This means that you can contain a given common-name to the > geographic region that it applies to. For example, there may be two > "Joe's Pizza". One is in Atlanta and the other is in New York. CNRP > allows you to specify the area in which you live so that when you look > up "Joe's Pizza" you don't get the one on the other side of the planet. > > 3.Unlimited character set -- A common name can include any > character in any language. > > In your common name you can include spaces, puncuation spaces, > exclamation marks, chinese language characters, etc. The options are > unlimited and allow you to best symbolize your name. > > > > > Examples > > Here are some examples. If you have our Internet Explorer plugin > installed then click below to see to it in action: > > > go:Microsoft > go:Network Solutions > go:Michael Mealling > > -- > James Love, Consumer Project on Technology > v. 1.202.387.8030, fax 1.202.234.5176 > [EMAIL PROTECTED], http://www.cptech.org > > > ___ > Random-bits mailing list > [EMAIL PROTECTED] > http://lists.essential.org/mailman/listinfo/random-bits >
Re: [IFWP] GOVERNMENT PROPOSES INTERNET NAMING LAW
Paul Twomey is history. He's been given the kiss of death. Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697 On Sun, 3 Sep 2000, Michael Sondow wrote: > > GOVERNMENT (of Australia) PROPOSES INTERNET NAMING LAW > > > > "If passed, the government claimed, it > will clarify existing provisions in the > Telecommunications Act 1997 for > the Australian Communications > Authority (ACA) and the Australian > Competition and Consumer > Commission (ACCC) to declare > and direct a manager of electronic > > addressing." > > Paul Twomey? > > > Michael Sondow > = > INTERNATIONAL CONGRESS OF INDEPENDENT INTERNET USERS >http://www.iciiu.org(ICIIU)[EMAIL PROTECTED] > Tel(718)846-7482Fax(603)754-8927 > = >
[IFWP] http://www.real-internet.org/
Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697
[IFWP] Hello ICANN - MYDOMAIN.COM faking auth on COM.BR zone (fwd)
This is the sort of network problem ICANN should be involved with. It a sad day when the registro de brazil has to go trolling on nanog for help. Joe Baptista http://www.dot.god/ dot.GOD Hostmaster +1 (805) 753-8697 Dear Nanog Readers, As we have not yet received any response from our abuse request (attached) to MYDOMAIN.COM and more 10 phone calls we are looking for help of any kind here. COM.BR zone is populated with 280K zone delegations (92% of the .BR registered domain names). Mydomain.com DNS servers are delegated to 1361 domains inside the .BR zone. We don't known why but these servers are answering authoritatively to COM.BR zone and they are carrying a wild card record to. This is causing some confusion and trouble to buggy resolvers (notably NT). If someone knows a contact different of the whois and the web site information please let me known asap privately. Best Regards Frederico Neves .BR tech contact --begin bash> dig @a.root-servers.net br ns ; <<>> DiG 8.2 <<>> @a.root-servers.net br ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 5 ;; QUERY SECTION: ;; br, type = NS, class = IN ;; ANSWER SECTION: br. 2D IN NSNS.DNS.br. br. 2D IN NSNS1.DNS.br. br. 2D IN NSNS2.DNS.br. br. 2D IN NSNS3.NIC.FR. br. 2D IN NSNS-EXT.VIX.COM. ;; ADDITIONAL SECTION: NS.DNS.br. 2D IN A 143.108.23.2 NS1.DNS.br. 2D IN A 200.255.253.234 NS2.DNS.br. 2D IN A 200.19.119.99 NS3.NIC.FR. 2D IN A 192.134.0.49 NS-EXT.VIX.COM. 2D IN A 204.152.184.64 ;; Total query time: 768 msec ;; FROM: clone.registro.br to SERVER: a.root-servers.net 198.41.0.4 ;; WHEN: Fri Sep 1 17:52:07 2000 ;; MSG SIZE sent: 20 rcvd: 209 bash> dig @NS.DNS.br. com.br ns ; <<>> DiG 8.2 <<>> @NS.DNS.br. com.br ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 3 ;; QUERY SECTION: ;; com.br, type = NS, class = IN ;; ANSWER SECTION: com.br. 1D IN NSNS2.DNS.br. com.br. 1D IN NSNS-EXT.VIX.COM. com.br. 1D IN NSNS.DNS.br. com.br. 1D IN NSNS1.DNS.br. ;; ADDITIONAL SECTION: NS2.DNS.br. 1D IN A 200.19.119.99 NS.DNS.br. 1D IN A 143.108.23.2 NS1.DNS.br. 1D IN A 200.255.253.234 ;; Total query time: 1 msec ;; FROM: clone.registro.br to SERVER: NS.DNS.br. 143.108.23.2 ;; WHEN: Fri Sep 1 17:52:24 2000 ;; MSG SIZE sent: 24 rcvd: 157 bash> dig @ns1.mydomain.com com.br any ; <<>> DiG 8.2 <<>> @ns1.mydomain.com com.br any ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 7 ;; QUERY SECTION: ;; com.br, type = ANY, class = IN ;; ANSWER SECTION: com.br. 42m40s IN SOA ns1.mydomain.com. hostmaster.com.br. ( 967828523 ; serial 4h33m4s ; refresh 34m8s ; retry 1w5d3h16m16s; expiry 42m40s ); minimum com.br. 3D IN NSns1.mydomain.com. com.br. 3D IN NSns2.mydomain.com. com.br. 3D IN NSns3.mydomain.com. com.br. 3D IN NSns4.mydomain.com. com.br. 1D IN A 208.184.130.40 com.br. 1D IN MX10 a.mx.mydomain.com. com.br. 1D IN MX10 b.mx.mydomain.com. com.br. 1D IN MX10 c.mx.mydomain.com. ;; ADDITIONAL SECTION: ns1.mydomain.com. 3D IN A 208.184.130.51 ns2.mydomain.com. 3D IN A 208.184.130.52 ns3.mydomain.com. 3D IN A 208.184.130.53 ns4.mydomain.com. 3D IN A 208.184.130.55 a.mx.mydomain.com. 1D IN A 208.184.130.53 b.mx.mydomain.com. 1D IN A 208.184.130.51 c.mx.mydomain.com. 1D IN A 208.184.130.55 ;; Total query time: 1022 msec ;; FROM: clone.registro.br to SERVER: ns1.mydomain.com 208.184.130.51 ;; WHEN: Fri Sep 1 17:52:46 2000 ;; MSG S
